nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Use the agent's ~/.dockercfg credentials doesn't stick

Javier Perez

Bamboo version: 6.5

Issue: When doing a docker push task configuration I select radio button Use the agent's ~/.dockercfg credentials and successfully save the task. However, when clicking back on the task configuration, bamboo has "reset" the option to Provide username and password. Not unexpectedly, the task execution fails with no basic auth credentials

Question: Why is this happening? How can I make bamboo accept the Use the agent's ~/.dockercfg credentials option?

Alternatively: Is it possible that the push task doesn't make a logout, so credentials are kept in .docker/config.json

Accepted answers

Gabriel Ribeiro

Hi @Javier Perez

I was able to reproduce the behavior and reported it as a bug:

Docker task - "Use the agent's ~/.dockercfg credentials" registry authentication type is not persisted

Please be sure to watch it, so that you are notified when this is fixed in a future release.

Thank you for reporting this.

All comments

Gabriel Ribeiro

Hi @Javier Perez

I was able to reproduce the behavior and reported it as a bug:

Docker task - "Use the agent's ~/.dockercfg credentials" registry authentication type is not persisted

Please be sure to watch it, so that you are notified when this is fixed in a future release.

Thank you for reporting this.

Javier Perez

Thank Gabriel. Well, this is the third bug we find in this release :-(

Would you have an answer to my other question? Is it possible that the push task doesn't make a logout, so credentials are kept in .docker/config.json?

Gabriel Ribeiro

Hi Javier,

The problem is that If you specify the credentials as part of the docker push task, Bamboo will always logout once it's done executing the task. Thus it will remove credentials associated to that registry from the config.json file

On previous Bamboo versions, there was a possibility to leave the credentials section empty so that Bamboo would not send a docker logout when the task finishes its execution but, since Bamboo 6.4 this is not possible anymore.

thanks

Javier Perez

So, this is my problem. It happens that my Dockerfile has a FROM that is pulling from my docker registry. I also need to pass arguments in the docker build command

docker build --build-arg arg=bla

Since the docker build task type in bamboo doesn't support build parameters I need to use the docker build in a bamboo script type task. After the build, the image is pushed to the docker registry using the docker push task type. Since the docker push task removes credentials from config.json, the next build, when docker build is called, won't find the credentials in config.json (having been removed by the the bamboo docker push in the previous bamboo run) so my build fails.

What's the solution for this? Pushing to the docker registry using a script type task?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

bamboo-administration