-
Notifications
You must be signed in to change notification settings - Fork 75
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
Inconsistent docker image mediatypes after caddy 2.7.5 #376
Comments
netsandbox
changed the title
Inconsitent docker image mediatypes after caddy 2.7.5
Inconsistent docker image mediatypes after caddy 2.7.5
Oct 29, 2024
This isn't managed in this repo, those tags etc are managed by the Docker Official Images build. /cc @tianon do you know what's going on here? I don't know about Docker image |
Thanks for the context! I'll close this, nothing actionable for us here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I currently debug a problem with our internal Quay container registry, where I can't mirror caddy images after 2.7.5 anymore.
With caddy 2.7.5, the docker image manifests had a consistent
mediaType
ofapplication/vnd.docker.distribution.manifest.v2+json
:This changed with 2.7.6, where all manifests has a
mediaType
ofapplication/vnd.oci.image.manifest.v1+json
,except for os windows, where the
mediaType
isapplication/vnd.docker.distribution.manifest.v2+json
:I actually don't know the container image specification, if it is allowed to have
application/vnd.oci.image.manifest.v1+json
andapplication/vnd.docker.distribution.manifest.v2+json
manifest in the same image, or if our Quay container registry should accept such images.golang, docker and traefik for example build their Linux and Windows docker images as separate tags. Maybe for a reason?
The text was updated successfully, but these errors were encountered: