You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We've got a private registry where we store our development/production images. Whenever I've changed the ./Dockerfile to use this image it stopped working in pipelines.
Something like this fails in my current testing setup and I cannot figure out why...
# authenticate with the Docker Hub registry
- docker login --username $DOCKER_HUB_USERNAME --password $DOCKER_HUB_PASSWORD $PRIVATE_REGISTERY
- docker pull $PRIVATE_REGISTRY:443/imagename
Docker build fails the same way. It will end up throwing a no basic auth error"
Error response from daemon: Get repository/image: no basic auth credentials
Wierd thing is, that when I manually run the same commands on my desktop it works. I've sanity checked that within the CI the ~/.docker/config.json contains the right values.
Docker login gives back `Login Succeeded`... I have the feeling that something within the CI might run under other users. I hope somebody has struggled with this already in the hopes to resolve this or debug to why this happens.
Well, we've figured it all out. At the time there was an issue with pipelines and we fixed that with a few commando's in the pipelines file itself. They have long fixed this and my post is no longer relevant.