Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Accessing Prive Docker Repository for Service Image

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:

 

...
definitions
:
services:

postgres:
image: postgres:11.5
variables:
POSTGRES_DB: 'postgres'
POSTGRES_USER: 'somePassword'

custom-app:
image: mydockerhubaccount/mycustomapp:latest-release
username: $DOCKER_HUB_USER
password: $DOCKER_HUB_PASSWORD
variables:
...  

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?

 

1 answer

1 accepted

1 vote
Answer accepted

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:

 

custom-app:
image:
name: mydockerhubaccount/mycustomapp:latest-release
username: $DOCKER_HUB_USER
password: $DOCKER_HUB_PASSWORD

Thank you so much!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

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...

197 views 2 1
Read article

Community Events

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

Events near you