You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, first off - thanks for continually supporting the Docker community!
Let me share about Perl/docker-perl#161 - it seems that official image versions from 9 years ago and older are now unavailable for new registry pulls. We noticed it for Perl 5.14, but it also affects other languages too:
$ docker pull perl:5.14
5.14: Pulling from library/perl
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/library/perl:5.14 to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
$ docker pull python:2.7.9-wheezy
2.7.9-wheezy: Pulling from library/python
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/library/python:2.7.9-wheezy to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
$ docker pull node:0.12.2
0.12.2: Pulling from library/node
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/library/node:0.12.2 to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
What's the general stance of official-images regarding this? Considering that these are all already unsupported by their respective communities, would it still make sense for Docker Hub to publish them? Or can there be something that helps transitioning the older image formats used in these older images to use the newest/supported manifest format (ideally without necessitating a full rebuild?)
The text was updated successfully, but these errors were encountered:
We had a recent discussion about this in docker-library/php#1522, and I'll copy my very relevant response here:
Unfortunately, this is a little complicated. I think docker/roadmap#173 is the roadmap issue for Docker at large, but some of the complexities for DOI are that we don't want to just "pull, convert, push" all these old images and have them show up as "updated", so ideally a solution here needs to happen without updating timestamps and that isn't something we can accomplish on our own. 🙇
Thank you for raising this though (and the user interest in it). ❤️
Thanks @tianon 👍 I agree with all points - I'd add that this is probably the sort of thing Docker Inc. could have made some prior official announcements, especially since a hint of this issue was already seen since 2021 and perhaps even earlier here in Perl/docker-perl#70.
Hello, first off - thanks for continually supporting the Docker community!
Let me share about Perl/docker-perl#161 - it seems that official image versions from 9 years ago and older are now unavailable for new registry pulls. We noticed it for Perl 5.14, but it also affects other languages too:
What's the general stance of official-images regarding this? Considering that these are all already unsupported by their respective communities, would it still make sense for Docker Hub to publish them? Or can there be something that helps transitioning the older image formats used in these older images to use the newest/supported manifest format (ideally without necessitating a full rebuild?)
The text was updated successfully, but these errors were encountered: