-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
[Bug]: Docker images were re-built and existing tags were overridden #255
Comments
I think the intention was to just re-build jdk8 from 8u342-b07 to 8u345-b01 with the changes (from curl to wget) in #242 The re-build of other images, i.e 17.0.4_8-* was a mistaken done in docker-library/official-images@955f86a . Either these non-jdk8 images should have new tags or in the original commit to add wget but keep curl till next release |
Is it possible to rebuild the overwritten tags to restore the previous state? Also, is it actually worth to break images in order to align? |
Hi all, So there's two parts to this issue. The rebuilding of existing tags is pretty common in the docker world, it's mostly done when security updates in the base image are published. The recent dependency change to remove curl and swap with wget does seem more inconvenient and would be considered a breaking change. The simplest option here would be to re-add curl as a dependency and publish the images again |
Please add the exact image (with tag) that you are using
eclipse-temurin:17.0.4_8-jre
Please add the version of Docker you are running
20.10.14
What happened?
A number of my applications are using
eclipse-temurin:17.0.4_8-jre
as their base image. Our Dockerfile usescurl
which was provided by the temurin base image up until recently. The issue is that the17.0.4_8-*
images were re-built and pushed to Docker Hub overriding what was there previously.For less specific tags like
latest
or17
perhaps that's fine but for a tag as specific as17.0.4_8-jre
I wouldn't expect the image to change once released, especially in a backwards incompatible manner (e.g. changing dependencies).This might be related to #68
Relevant log output
The text was updated successfully, but these errors were encountered: