-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Push multi-arch manifests to quay.io #4227
Comments
To mitigate pulling limits in Docker Hub. Calico currently offers official images in Quay, however they do not support multi-arch manifest, so for the time being we need to use manually built manifests based on images from Quay. This issue is reported to upstream Calico: projectcalico/calico#4227 Part of #1225. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
When we implemented our release infrastructure quay.io did not support multi-arch manifests, and so we have separate images pushed to quay. If quay.io now supports multi-arch manifests, that is great news! We should update our release process to publish those as well. |
It seems this is now fixed:
|
@invidian I think you closed this by mistake as the Quay.io images still do not have ARM64 support... |
Indeed, it seems at least one of the image is still missing ARM64 support: $ docker manifest inspect quay.io/calico/cni:v3.19.1
{
"schemaVersion": 2,
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"config": {
"mediaType": "application/vnd.docker.container.image.v1+json",
"size": 3363,
"digest": "sha256:5749e8b276f9b5aea2683d8a0d59afd05a2be478f5092fbaadc4715f4db76e5a"
},
"layers": [
{
"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
"size": 18093,
"digest": "sha256:740c37ed87bd03bc3193d1382b3b836328022c78911d62d0f9b508d9a37abc1a"
},
{
"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
"size": 4063,
"digest": "sha256:5019aa621b5376714f3e9aa04a6f264a857f639c536a587b5a1670b1e2699e62"
},
{
"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
"size": 48310687,
"digest": "sha256:b0c76401258249c3fb3308cde0f71a626d225a5ede0dcef81c23b430cbb716da"
}
]
} |
Fixed in
|
Awesome! |
Expected Behavior
Replacing
calico/cni:v1.17.0
withquay.io/calico/cni:v1.17.0
should work on ARM platforms.Current Behavior
quay.io
registry is returning different manifests thandocker/io
, even though Quay supports multi-arch manifests.Manifest from
docker.io
:Manifes from
quay.io
:Sample multi-arch manifest from
quay.io
:Context
Because of new Docker Hub pull limits, we would like to use Quay as a main registry to pull Calico images from, to make cluster creation process more reliable (kinvolk/lokomotive#1225), as currently we sometimes hit limits when creating virtual clusters (so using the same public IP all the time).
The text was updated successfully, but these errors were encountered: