Bamboo Docker Push fails

Vlad Budica

Hi guys,

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 vlad@gmail.com', 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 ?

Thanks,
Vlad

Steffen Opel [Utoolity]

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.