Tag points to wrong manifest in multi-arch build

[aidangoettsch]

I'm building images for AMD64 and ARM64 at the same time from the same Dockerfile and the resulting tag frequently points to a single architecture image (usually, but not always the ARM64 image), not the multi-image manifest. The images are being pushed to ACR and the builds are running on Azure Pipelines

Build command:

docker buildx build --platform linux/amd64,linux/arm64 --cache-from ***/pipelines-cache:qt-base --cache-to type=registry,ref=***/pipelines-cache:qt-base,mode=max -t ***/qt-base-dev:[commit hash] -t ***/qt-base:[semver] --target base base-image --push

[tonistiigi]

If this happens temporarily during push then it is an issue that has been fixed and will be in the next release. Otherwise, need a repro.

[aidangoettsch]

Looks like #2020 is the fix you're talking about? This might be causing our issue, we've seen ACR have some weird quirks with replication and response caching (ex. pushes don't reflect for 3-5 minutes sometimes) and I could see pushing multiple tags in a row quickly leading to some of those getting lost. I'll try to test the pipeline with 0.9.0-rc2 and see if that helps.

[aidangoettsch]

Got 0.9.0 deployed and it looks like this is fixed.