how can i configure Job -> Docker to authorize with my private docker registry?
i'm getting 403 when downloading private docker image e.g. private/docker-image:1.2.3
If the private image is in a registry which does not require authentication you can just use the registry url in the Docker image field.
If your registry requires authentication, it becomes a little more complicated.
You will need to set up a script on the agent server which will run the docker login command. (in ~/.profile for example)
docker login -u <myuser> -p <mypassword> registryurl
Once this is configured and the remote agent has sourced the new script, it will be able to connect to the private image registry. You can test this by attempting a docker pull for your desired image.
You will need to configure the above for all remote agents which will need to connect to the private registry.
If your credentials remain the same, you can re-run the docker login command to re-authorize your agent. (you should be able to automate this with a chron job).
If your credentials have expired/rotated, you'll need to modify your script to use the new credentials.
I meant to reply to this and forgot to yesterday. I found this solution from AWS Labs that pretty much solves the problem for me for ECR repositories:
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 ...
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