unexpected status from HEAD request to {{registry}}: 401 Unauthorized

[ariwijayaikd]

anyone have this issue? image has been built but can't be push to registry

#21 exporting to image
#21 pushing layers 4.2s done
#21 ERROR: failed to push {{registry}}/satudikti/be:v3.0.369: unexpected status from HEAD request to {{registry}}/v2/{{project}}/be/blobs/sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1: 401 Unauthorized
------
 > exporting to image:
------
ERROR: failed to solve: failed to push {{registry}}/{{project}}/be:v3.0.369: unexpected status from HEAD request to {{registry}}/v2/{{project}}/be/blobs/sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1: 401 Unauthorized
Error: buildx failed with: ERROR: failed to solve: failed to push {{registry}}/{{project}}/be:v3.0.369: unexpected status from HEAD request to {{registry}}/{{project}}/be/blobs/sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1: 401 Unauthorized

info:

• {{registry}} refer to my private registry
• {{project}} refer to project name

[ariwijayaikd]

here case in the past week ago when it succeed

#21 exporting to image
#21 pushing layers 20.2s done
#21 pushing manifest for {{registry}}/{{project}}/be:v3.0.366@sha256:9c97e11e2bb369ae2bb799b80bbe448[326](https://github.com/{{repository}}/actions/runs/8701003983/job/23862820785#step:9:331)73af49350dc42ded176dc1f7bf26f3
#21 pushing manifest for {{registry}}/{{project}}/be:v3.0.366@sha256:9c97e11e2bb369ae2bb799b80bbe44832673af49350dc42ded176dc1f7bf26f3 1.7s done
#21 pushing layers 0.5s done
#21 pushing manifest for {{registry}}/{{project}}/be:latest@sha256:9c97e11e2bb369ae2bb799b80bbe44832673af49350dc42ded176dc1f7bf26f3
#21 pushing manifest for {{registry}}/{{project}}/be:latest@sha256:9c97e11e2bb369ae2bb799b80bbe44832673af49350dc42ded176dc1f7bf26f3 1.1s done
#21 DONE 24.3s

[alaugks]

I guess or am even sure that it is a temporary issue at AWS. I had a similar issue.

[alaugks]

See this discussion: #983