I am doing a docker push build step and I get the following error:
error 04-Aug-2017 14:49:37 Caused by: com.atlassian.utils.process.ProcessException: Error executing '/usr/bin/docker login -u vlad -p ***** -e firstname.lastname@example.org', exit code: 125
error 04-Aug-2017 14:49:37 at com.atlassian.bamboo.plugins.docker.process.DefaultDockerProcessService.execute(DefaultDockerProcessService.java:53)
error 04-Aug-2017 14:49:37 at com.atlassian.bamboo.plugins.docker.process.DefaultDockerProcessService.executeSilently(DefaultDockerProcessService.java:63)
error 04-Aug-2017 14:49:37 at com.atlassian.bamboo.plugins.docker.process.DockerTaskProcessService.executeSilently(DockerTaskProcessService.java:75)
error 04-Aug-2017 14:49:37 at com.atlassian.bamboo.plugins.docker.client.DockerCmd$AuthorisedCommand.login(DockerCmd.java:346)
error 04-Aug-2017 14:49:37 at com.atlassian.bamboo.plugins.docker.client.DockerCmd$AuthorisedCommand.execute(DockerCmd.java:311)
error 04-Aug-2017 14:49:37 at com.atlassian.bamboo.plugins.docker.client.DockerCmd.push(DockerCmd.java:238)
The docker login command doesn' t have a -e option and that generates the issue.
Do you have any suggestions?
Is this a bug ?
The -e and --email flags flags have been removed from Docker engine as of release 17.06, so presumably the Docker CLI on your agents is a more recent version.
I don't know off hand how the Bamboo Docker task handles this, but given that all fields are optional because you can "Leave these credentials empty to use the agent's ~/.dockercfg credentials" (which would also be a workaround accordingly), it might just do the right thing and skip the -e flag when you don't specify an email address.
Hello @Vlad Budica,
It's known issue https://jira.atlassian.com/browse/BAM-18613 which is fixed in Bamboo 6.2.0 planned for release end of September.
You can try updated version of docker plugin from https://bitbucket.org/atlassian/bamboo-docker-plugin/downloads/ for older versions of Bamboo, but we not guarantee it is 100% compatible
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot