failed commit on ref — unexpected status: 401 UNAUTHORIZED

[Jake Goulding]

Howdy all!

I'm trying to set up a cached multi-stage build where each stage is pushed to quay.io. This was close to working, but I'm receiving an HTTP 401 response when pushing an image that shouldn't have changed:

exporting to image

exporting layers done

exporting manifest sha256:4acf896cde5eb40ec7cfbd8b7bc46315dfafa19c554946dc49d0e5addb58117e done

exporting config sha256:bcd76e41e5110b03de346fe4aa205f3d5f4bb30c639d7c6358d510b27a993547 done

pushing layers

pushing layers 0.2s done

pushing manifest for quay.io/shepmaster/rust-playground-ci-rust-stable:toolchain--399808422

pushing manifest for quay.io/shepmaster/rust-playground-ci-rust-stable:toolchain--399808422 0.4s done

ERROR: failed commit on ref "manifest-sha256:4acf896cde5eb40ec7cfbd8b7bc46315dfafa19c554946dc49d0e5addb58117e": unexpected status: 401 UNAUTHORIZED

This shouldn't be a problem like a bad username or password as I've successfully logged in and pushed/pulled with these credentials.

I'm [not the only] person who has experienced this. That user said that targeting GitHub Container Registry instead of Quay worked. Is there a workaround I can use other than switching registries?

I'm actively banging around with my CI setup, but you can take a look at a [recent run] if you are interested.

-Jake

[not the only]: https://github.com/docker/buildx/issues/327#issuecomment-733058083
[recent run]: https://github.com/integer32llc/rust-playground/runs/1496597523