-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JIB mode: Loading tar into docker daemon fails #1385
Milestone
Comments
The tar file created with d-m-p 0.34.1 seems to contain the image in the OCI format, which doesn't seem to be supported by "docker load".
For comparison, the contents of the tar file created with 0.34.0:
|
rohanKanojia
added a commit
to rohanKanojia/docker-maven-plugin
that referenced
this issue
Oct 2, 2020
…thodEror + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix fabric8io#1385
rohanKanojia
added a commit
to rohanKanojia/docker-maven-plugin
that referenced
this issue
Oct 2, 2020
…thodEror + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix fabric8io#1385
rohanKanojia
added a commit
to rohanKanojia/docker-maven-plugin
that referenced
this issue
Oct 2, 2020
…thodEror + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix fabric8io#1385
rohanKanojia
added a commit
to rohanKanojia/docker-maven-plugin
that referenced
this issue
Oct 2, 2020
…thodEror + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix fabric8io#1385
rohanKanojia
added a commit
to rohanKanojia/docker-maven-plugin
that referenced
this issue
Oct 2, 2020
…thodEror + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix fabric8io#1385
rohanKanojia
added a commit
to rohanKanojia/docker-maven-plugin
that referenced
this issue
Oct 2, 2020
…thodEror + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix fabric8io#1385
rhuss
added a commit
that referenced
this issue
Oct 10, 2020
…1386) + Updating jib-core to 0.15.0 broke our current JIB support due to incompatibility with httpclient. Updated apache httpclient to 4.5.10 + Somehow behavior of Jib setting ImageFormat has been changed(maybe it was not working earlier. Introduced a new parameter in mojo `docker.build.jib.imageFormat` to allow users specify image format(OCI or Docker) with Docker as default ImageFormat. + Minor Cleanup in Integration tests; Added an integration test for JIB mode which builds image tarball and verifies it by loading into docker daemon This should also fix #1385 Co-authored-by: Roland Huß <roland@ro14nd.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Tested with the Spring Boot Sample with JIB Build Mode:
When adapting the pom of the 'spring-boot-with-jib' sample to use d-m-p
0.34.0
the tar file can be successfully built and loaded into docker withdocker load -i <tar-file>
, as described in the README of the sample.But when adapting the pom to use
0.34-SNAPSHOT
, having built d-m-p with theorg.apache.httpcomponents:httpclient
dependency updated to 4.5.10 (as fix for the JIB build errors, see #1384), the successfully built tar file can't be loaded into docker.docker load -i <tar-file>
returns an error:So, this issue seems to have been introduced with d-m-p
0.34.1
.Info
mvn -v
) : 3.6.0The text was updated successfully, but these errors were encountered: