Docker runner -> running docker container leads to not found error



my job contains of

  • setup_remote_docker step,
  • docker run hello-world command
  • go test run that has tests that running docker containers

during the execution of this job docker run hello-world works fine

Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world

Digest: sha256:66ef312bbac49c39a89aa9bcc3cb4f3c9e7de3788c944158df3ee0176d32b751
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:

For more examples and ideas, visit:

however tests fail with error

--- FAIL: TestDirents (0.06s)
	Error Trace:	awstest.go:43
	Error:		Received unexpected error Post http://unix.sock/containers/create?: dial unix /var/run/docker.sock: connect: no such file or directory

Is it possible to fix this?


The hello-world app, as far as I know, prints some stuff and then exits immediately. I don’t think it contains tests, but when you get to running tests, it will have exited by that point anyway.


I believe this is because the Docker socket isn’t exposed. Try changing this line:

docker run hello-world


docker run -v /var/run/docker.sock:/var/run/docker.sock hello-world

closed #4