Qingchuan Hao

`docker login -u ${AZURE_CLIENT_ID} -p ${AZURE_CLIENT_SECRET} ${REGISTRY}` before `docker buildx build --push` can work as a workaround.

Thanks for the investigation from @northtyphoon, here is my copy and paste of his reply: The above conditions will run into a corner case and hit a buildkit bug (https://github.com/moby/buildkit/blob/ffe2301031c8f8bfb8d5fc5034e5e509c5624913/session/auth/authprovider/authprovider.go#L91)...

@andyzhangx https://github.com/kubernetes/kubernetes/pull/95950 hope this is useful for reference?

May I ask what action is performed to have these changes? and how do we know the new modules have no secure issue? Thanks.

Please ignore AKS Windows VHD pipeline Check. I am fixing this.

take an arm64 image push for example. ``` ➜ external-dns git:(docker-buildx-for-multi-arch) IMAGE=qingchuanhao.azurecr.io/external-dns/external-dns ARCH=arm64 make build.push ➜ external-dns git:(docker-buildx-for-multi-arch) docker manifest inspect qingchuanhao.azurecr.io/external-dns/external-dns:external-dns-helm-chart-1.3.2-17-g4bac670e-dirty-arm64 --verbose { "Ref": "qingchuanhao.azurecr.io/external-dns/external-dns:external-dns-helm-chart-1.3.2-17-g4bac670e-dirty-arm64", "Descriptor": { "mediaType": "application/vnd.docker.distribution.manifest.v2+json",...

`ARCH=arm64 make build.docker` returns the following error, which should have been fixed in https://github.com/golang/go/commit/f84d28b7755f256efda7830a3b78b46464497527 by ignoring the error `unsupported VMA range` ``` #16 1432.7 FATAL: ThreadSanitizer: unsupported VMA range #16...

ping @Raffo @RaffoRaffo, PTAL, thanks.

@cheftako , could we move forward with this PR? Thanks.

Hi @andyliuliming, this change is waiting for review, hope the problem fixed in this PR does not confuse too many users.