-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Deprecation of image formats in older published images #16997
Comments
Thank you for filing the issue. 🙇 ❤️ We had a recent discussion about this in docker-library/php#1522, and I'll copy my very relevant response here:
|
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. |
FYI I got the same request: https://jira.mariadb.org/browse/MDEV-35114 |
Ideally, we'd love to be able to convert these in-place on Docker Hub, but there's a lot of complexity in doing so that currently prevents the possibility. If you have a tool which does not support schema1 and you still need to work with these older images, I have written https://github.com/tianon/oci-schema1 to help perform the conversion without any runtime support ( |
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: