You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the image used in the dind sidecar is any later than :18.09-dind (15 months old at this point, and verrrry far out of the support window), Docker operations fail:
[client] docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
[client] See 'docker run --help'.
[client] time="2020-01-23T19:59:54Z" level=error msg="failed to dial gRPC: cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory"
[client] error during connect: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=xjdfz63zazhjfy3hi2th0x5yl&shmsize=0&t=hello&target=&ulimits=null&version=1: context canceled
[client] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[client] docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
[client] See 'docker run --help'.
/kind question
The text was updated successfully, but these errors were encountered:
.../var/run/docker.sock is not shared by the docker:dind container and the docker binary tries to use it by default.
To overwrite this and make the client use TCP to contact the Docker daemon, in the other container, be sure to include the environment variables of the build container:
DOCKER_HOST=tcp://localhost:2375 for no TLS connection.
DOCKER_HOST=tcp://localhost:2376 for TLS connection.
Make sure to configure those properly. As of Docker 19.03, TLS is enabled by default but it requires mapping certificates to your client. You can enable non-TLS connection for DIND or mount certificates as described in Use Docker In Docker Workflow with Docker executor
Found while iterating on #1928
If the image used in the dind sidecar is any later than
:18.09-dind
(15 months old at this point, and verrrry far out of the support window), Docker operations fail:/kind question
The text was updated successfully, but these errors were encountered: