-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Docker Tag Change #937
Comments
Our Dockerfiles have had things like this:
Now that Debian 9 stretch has Changing tags like this is really not compatible upgrade. It breaks quite lot of builds around there. |
I'm wondering if this issue is affecting my builds, too. I have a repo that pulls |
We are improving how the tags are handled between the different versions of Debian in #850. We will be providing tags to pin the version of Debian while the tag without the prefix will refer to the default version of Debian, which will change over time. |
We're facing issues with our builds too. Wondering if the tagging refactor being mentioned here has anything to do with it #936 |
Can we close this since now you can easily target which debian version you want to use? |
Yeah you can close it. My main purpose was to just let people know going from Jessie to Stretch was a breaking change. |
It looks like the tags were changed recently which caused a breaking change with out build/application.
We have been using node:dubnium for the past week with no problems, and then today our builds failed due to the docker container.
It appears the node:dubnium was changed to point to debian stretch instead of debian jessie. Jessie had some files that our application depended on that stretch does not.
We have fixed the issue for our build by switching to use node:dubnium-jessie instead.
Not sure if this was an intended change (or if we were using tags wrong). Just figured I should let people know that a tag change had some repercussions.
The text was updated successfully, but these errors were encountered: