Closed varshavaradarajan closed 6 years ago
Ah, I see now that I probably need to run the DinD agent in "privileged mode":
Docker in Docker (DinD) [...] This requires that the host docker container be run in privileged mode. [...]
...alternatively:
Tip: Check the 'Privileged mode' checkbox which is essential to run the Docker in Docker image.
@varshavaradarajan How do I use this?
The GoCD DinD agent starts and registers in the GoCD server successfully, but the Docker engine doesn't start inside it, so jobs needing Docker fail on this agent.
This is what I get in the
/usr/local/bin/nohup.out
file inside the container of the DinD agent:I get the same output if I run the command myself manually inside the container:
sh -c "$(which dind) dockerd --host=unix:///var/run/docker.sock --host=tcp://0.0.0.0:2375 --storage-driver=vfs"