It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Docker build failed: no such container:path Edited

I have a docker container:

/usr/bin/docker run --volume /home/bamboo/builds/xml-data/build-dir/360449/WEBSITE-BD-JOB3:/home/bamboo/builds/xml-data/build-dir/360449/WEBSITE-BD-JOB3 --volume /var/atlassian/application-data/bamboo/temp:/var/atlassian/application-data/bamboo/temp --detach --name 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564 --net=host shamilnunhuck/kaniko-debug:shell tail -f /dev/null

and I assume Bamboo is trying to copy my script over?

/usr/bin/docker cp /opt/atlassian/bamboo/temp/initialiseDockerContainer.sh7168219084128755568.tmp 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564:/tmp/initialiseContainer.sh

However, it fails:

Error: No such container:path: 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564:/tmp
Exit code: 1, output: STDOUT:  Beginning to execute external process for build 'Shamil Website - Build - Publish Image #25 (WEBSITE-BD-JOB3-25)'\n ... running command line: \n/usr/bin/docker cp /opt/atlassian/bamboo/temp/initialiseDockerContainer.sh7168219084128755568.tmp 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564:/tmp/initialiseContainer.sh\n ... in: /home/bamboo/builds/xml-data/build-dir/360449/WEBSITE-BD-JOB3\nSTDERR: Error: No such container:path: 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564:/tmp
Failed to start docker container 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564
com.atlassian.bamboo.docker.DockerException: Error running Docker run command
        at com.atlassian.bamboo.docker.DockerContainerServiceImpl.run(DockerContainerServiceImpl.java:130)
        at com.atlassian.bamboo.v2.build.agent.docker.DockerContainerControllerImpl.startContainerIfRequired(DockerContainerControllerImpl.java:98)
        at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:154)
        at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.lambda$waitAndPerformBuild$0(BuildAgentControllerImpl.java:130)
        at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:118)
        at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:124)
        at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.lambda$start$0(DefaultBuildAgent.java:108)
        at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:48)
        at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:26)
        at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:17)
        at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:41)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.atlassian.utils.process.ProcessException: Error executing /usr/bin/docker cp /opt/atlassian/bamboo/temp/initialiseDockerContainer.sh7168219084128755568.tmp 511d9b8d-cd36-4d53-92c9-78a94c2be6795570564:/tmp/initialiseContainer.sh
        at com.atlassian.bamboo.docker.DockerContainerServiceImpl.execute(DockerContainerServiceImpl.java:302)
        at com.atlassian.bamboo.docker.DockerContainerServiceImpl.execute(DockerContainerServiceImpl.java:273)
        at com.atlassian.bamboo.docker.DockerContainerServiceImpl.run(DockerContainerServiceImpl.java:112)
        ... 11 more

Bamboo can delete the container, so I assume it's still running. Any ideas why it's failing?

1 answer

Is this log output coming from a Docker task running a "Build a Docker image" command?

Also, what version of Bamboo are you running?

This is the output of the first task (which is a script) for.a job which is isolated by docker.

 

I'm using Bamboo 7.0.4. 

I'm sorry I may not be of much help - I've used Bamboo to build Docker containers, but haven't used isolated Docker containers to build apps.

FWIW: It would appear that Bamboo is attempting to load the image shamilnunhuck/kaniko-debug:shell in the first line.  I would guess that is failing and therefor why the cp command is failing.  When you run a docker image, it's possible for it to "succeed" however if the process running inside the container fails or quits, the container will stop and no longer be available.

If you have SSH access to your Bamboo server, you can try poking around in the Docker registry to see if that image exists - then try running it with the -i command instead of the --detach to see what's happening... just some ideas.

I figured it out - the tmp path didn't exist on the container.

LOL - so exactly what the error said... of course!

Glad you figured it out!

Like Shamil_Nunhuck likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Using Bamboo with new Bitbucket Cloud authentication

...roperties: -Dbamboo.bitbucket.cloud.use.workspace.api=true There are patches available for Bamboo versions 6.8.3, 6.9.2, and 6.10.5 on the bug report that add support for the System Property. T...

251 views 0 5
Read article

Community Events

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

Events near you