I am trying to access a docker image for a service in a bitbucket build. The build fails with the following message:
rpc error: code = Unknown desc = failed to resolve image "docker.io/mydockerhubaccount/mycustomapp:latest-release": no available registry endpoint: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
The image resides in a private docker hub repository, and I have configured the 'custom-app' service as follows:
The username and password are valid and configured correctly as BitBucket Repository variables (we use the same variables in the same pipeline to push images to the same private docker hub repository). I have also confirmed that the image is available on the docker hub repo by pulling it independently on my development machine.
Is there something missing in my configuration that would cause this error?
Looks like the problem was a result of not including a 'name
attribute. If you are using a private repo, you need to declare the image name like so:
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events