1
0

Specific error for socket permission

As discussed here: https://github.com/nginx-proxy/acme-companion/issues/1054

If socket is not readable, for example when protected with SELinux and/or run as a rootless user, the existing error is deceptive. An additional error to check that it is readable before checking if it is a socket will clarify the problem. SELinux tip included for good measure.
This commit is contained in:
John Mertz 2024-09-10 20:02:17 -06:00 committed by GitHub
parent e15381bc1b
commit 517d59438c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

@ -14,6 +14,11 @@ function print_version {
function check_docker_socket {
if [[ $DOCKER_HOST == unix://* ]]; then
socket_file=${DOCKER_HOST#unix://}
if [[ ! -r $socket_file ]]; then
echo "Error: Docker host socket at $socket_file is not readable. Please check user permissions" >&2
echo "If you are in a SELinux environment, try using: '-v /var/run/docker.sock:$socket_file:z'" >&2
exit 1
fi
if [[ ! -S $socket_file ]]; then
echo "Error: you need to share your Docker host socket with a volume at $socket_file" >&2
echo "Typically you should run your container with: '-v /var/run/docker.sock:$socket_file:ro'" >&2