Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Windows Docker agent

Eric Fossum February 5, 2019
05-Feb-2019 07:47:17    Beginning to execute external process for build 'Ericfoss Testing - Python Unit Tests - Job 1 #19 (ET-PUT2-JOB1-19)'
... running command line:
C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --volume C:\Bamboo\xml-data\build-dir\ET-PUT2-JOB1:C:\Bamboo\xml-data\build-dir\ET-PUT2-JOB1 --volume C:\Bamboo\temp:C:\Bamboo\temp --detach --name 85fbf790-981e-4f9e-9b79-bc4748542ba0 --net=host aft_docker:latest tail -f /dev/null
... in: C:\Bamboo\xml-data\build-dir\ET-PUT2-JOB1
05-Feb-2019 07:47:17    b36e42dd2c7a635f3f4de5f9c2ca4a789e54798303ff95b3d96d34d3355f2038
05-Feb-2019 07:47:23    C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: container b36e42dd2c7a635f3f4de5f9c2ca4a789e54798303ff95b3d96d34d3355f2038 encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2)

I got this error while trying to run a Windows Docker container. The first time I tried I got a network error no host network found, so I just created one. Now it says it can't find a file, but I'm not sure which file it's trying to find. The plan is as simple as it gets


  key: ET
    key: PUT2
    name: Python Unit Tests

dockerImage: aft_docker:latest
  - jobs:
    - requirements:
        - windows
      interpreter: cmd
        - dir



So Windows is missing the tail command, but you can get it from Microsoft in the Resource Kit. Now I get a different error.

06-Feb-2019 10:45:43

Beginning to execute external process for build 'Ericfoss Testing - Windows Docker Test - Default Job #3 (ET-WDT-JOB1-3)'

... running command line:

C:\Program Files\Docker\Docker\Resources\bin\docker.exe cp C:\Users\ericfoss\AppData\Local\Temp\initialiseDockerContainer.sh8410030257533708691.tmp f4d5b276-a36a-4bcb-b54e-4d98efb9db5a:/tmp/

... in: C:\Bamboo\xml-data\build-dir\ET-WDT-JOB1

06-Feb-2019 10:45:43    Error response from daemon: filesystem operations against a running Hyper-V container are not supported

06-Feb-2019 10:45:43    Failed to start docker container f4d5b276-a36a-4bcb-b54e-4d98efb9db5a

06-Feb-2019 10:45:43    com.atlassian.bamboo.docker.DockerException: Error running Docker run command


1 answer

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 9, 2019



Have you updated to latest version of container? 

After googling your error I met this article


I hope it helps



Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events