Closed
Description
Hello from the rustup team!
Coming from Rustup v1.28.0 release blocked by Docker pull error, we've noticed that our recent release CI has failed with essentially the following errors (rustup's cross-compiling CI workflows are relying on rust's images to function correctly):
ERROR: failed to solve: rust-aarch64-unknown-linux-musl: failed to resolve source metadata for docker.io/library/rust-aarch64-unknown-linux-musl:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
ERROR: failed to solve: rust-arm-unknown-linux-gnueabi: failed to resolve source metadata for docker.io/library/rust-arm-unknown-linux-gnueabi:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Looking at our mapping, these two names point to the same image in this repo:
aarch64-unknown-linux-musl) image=dist-arm-linux ;;
arm-unknown-linux-gnueabi) image=dist-arm-linux ;;
Since this issue is ARM Linux-exclusive, I'm convinced that #133809 #133902 is the direct cause of this issue.
Is it possible to revert the relevant Dockerfile deletion(s) or at least keep the old Dockerfile(s) for a while? We can migrate immediately after we're granted access to ARM64 Linux CI runners (but not just yet).
Many thanks in advance! 🙇
(cc @Kobzol)