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

Push a Docker Image to custom registry: Login fails

I've setup a custom docker registry and configured it to use htpasswd authentication.  I have tested logging into the repository successfully by browsing to https://<repo>/ v2/_catalog - and also from Powershell using the Docker login command using the same command from my log file (using "type password.txt | docker login...") to pass the password using --password-stdin.

So I've proven that I can login to my repository with proper credentials.

I've setup a task using command "Push a Docker Image to a Docker registry" and select "Custom Registry".

I've selected "Provide username and password" and type in the correct username and password used previously in both the browser and the Powershell command.

When I run my plan, this task fails showing the following from the logs:

Not logged in to my.repo.com:5000

Error occurred while running Task 'Push SisenseSSOHandler Docker image to registry on Elderberry(3)' of type com.atlassian.bamboo.plugins.bamboo-docker-plugin:task.docker.cli.com.atlassian.bamboo.task.TaskException: Failed to execute task

...

Caused by: com.atlassian.utils.process.ProcessException: Error executing '/usr/bin/docker login -u username --password-stdin my.repo.com:5000', exit code: 1

What frustrates me is that I copied that last command and successfully logged in using Powershell.  

I'm running Bamboo 7.0.3 build 70016 on CentOS 7 with Docker 19.03.9.

What am I missing?  If you need more information I'm happy to provide it.  Thanks in advance.

1 answer

1 accepted

1 vote
Answer accepted

Found my solution.  Our servers are VMs in Google Cloud and the Bamboo server was resolving my.repo.com with the external IP address (which is blocked by the firewall rules) - so I modified the /etc/hosts file on Bamboo to point my.repo.com to the internal IP address and now it logs in just fine!

Hope this helps someone else!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

251 views 4 6
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