Docker push failed: unauthorized: authentication required

Issue #15501 resolved
Yaxing Chen created an issue

Our pipeline pushes docker image to a private owned registry. It has been working until few days ago. Docker pushes started failing due to unauthorized: authentication required errors.

Please see log as following:

docker login --username=$CCE_REGISTRY_UNAME --password=$CCE_REGISTRY_PWD <registry>
+ docker login --username=$BAIDU_CCE_REGISTRY_UNAME --password=$BAIDU_CCE_REGISTRY_PWD <registry>
Login Succeeded
docker build -t <registry>/<namespace>/<image>:$BITBUCKET_TAG .
docker push <registry>/<namespace>/<image>:$BITBUCKET_TAG
30m 16s
+ docker push <registry>/<namespace>/<image>:$BITBUCKET_TAG
The push refers to a repository [<registry>/<namespace>/<image>]
d7c237ef87fc: Preparing
69cc5717c281: Preparing
5b1e27e74327: Preparing
04a094fe844e: Preparing
5b1e27e74327: Pushed
04a094fe844e: Pushed
69cc5717c281: Retrying in 5 seconds
69cc5717c281: Retrying in 4 seconds
69cc5717c281: Retrying in 3 seconds
69cc5717c281: Retrying in 2 seconds
69cc5717c281: Retrying in 1 second
69cc5717c281: Pushed
unauthorized: authentication required

As you can see, login was successful, it managed to push some part of the image, then eventually failed due to unauthorized: authentication required.

Did anything change recently that could cause this? Can you help debugging on this?

(Pushing from localhost using the exact same steps works fine)

Comments (6)

  1. Matt Ryall

    Apologies for not replying to this sooner. Your ticket was just recently brought to my attention.

    Can you please advise if you're still having this problem? We had some backend issues with Bitbucket during this period in January, so it is hopefully now resolved.

  2. Yong Feng

    @mryall_atlassian May I know how it is resolved? I recently met the same issue that "unauthorized: authentication required" is shown in the middle of pushing an image to a docker registry. The image actually is pushed successfully.

  3. Log in to comment