★ kubernetes: force-refresh a cached multi-architecture image 0 ▲ ¬ just serendipity 🍀 33 minutes ago · Tech · hide · 0 comments ♠ Previously. Problem statement: a Kubernetes ARM64 node kept running an AMD64 image after I replaced the registry tag with a multi-architecture image via skopeo, due to image caching. I first mirrored only the AMD64 variant into AWS ECR (note: no --all): % skopeo sync \ --dest-creds "AWS:$(aws ecr get-login-password --region cn-north-1)" \ --src docker --dest docker \ --override-os linux --override-arch amd64 \ quay.io/argoproj/argocd:v3.5.0 \ "$REGISTRY/quay.io/argoproj" That image failed on the ARM64 node: exec /usr/local/bin/argocd: exec format error The source has four platform manifests, so I replaced the ECR tag with the full manifest list (-all1): % skopeo sync \ --all \ --dest-creds "AWS:$(aws ecr get-login-password --region cn-north-1)" \ --src docker --dest docker \ quay.io/argoproj/argocd:v3.5.0 \ "$REGISTRY/quay.io/argoproj" linux amd64 sha256:521d6b62ecd0434c9cc6e9242a74f0e1137bb8fc0026b2c483ea88f3f17e725d linux arm64… No comments yet. Log in to reply on the Fediverse. Comments will appear here.