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
Docker does not allow for read-only mounts of sockets at this point.
This can be tested by running:
❯ docker run --rm -it -v /var/run/docker.sock:/tmp/docker.sock:ro \
docker ls -l /tmp/docker.sock
srw-rw---- 1 root 967 0 Apr 13 16:16 /tmp/docker.sock
❯ docker run --rm -it -v /var/run/docker.sock:/tmp/docker.sock:ro \
docker /usr/local/bin/docker -H unix:///tmp/docker.sock ps |wc -l
17
Even if docker supported read-only sockets, you would not want it to be
read-only if you are using `-notify-sighup` because then the docker socket is
used to communicate to the other container to notify it.
This change in documentation reflects the fact that the socket will be writable.
0 commit comments