Rootless docker and symlink to docker.sock security issues

Submitted ⁨⁨1⁩ ⁨day⁩ ago⁩ by ⁨Guadin@k.fe.derate.me⁩ to ⁨selfhosted@lemmy.world⁩

I changed my docker installation to rootless. I now installed Patchmon on the host and I wanted to monitor and update my Docker images as well. But Patchmon requires docker.sock to be in /var/run. My current docker.sock is of course in /run/user/{userid}. Are there any security risks, and if so what are they, to making a symlink to have the docker.sock in /var/run as well? The /run/user/{userid}/docker.sock is owned by the user running Docker. The symlink is owned by root because of the privileges needed for /var/run.

I don't have enough knowledge to be doing these kind of things, but I just like to tinker and I want to know how insecure this setup could be.

original

Comments

Sort:hotnew top

groet@feddit.org ⁨21⁩ ⁨hours⁩ ago
is there a reason you don’t use podman instead of rootless docker?

can you run patchmon inside of docker and mount the socket to the original path inside of the container?

the symlink has the file permissions of the file it points to. If the socket is owned by a user, so will the symlink, even if you used root/sudo to create the link. (technically the symlink will be owned by root, but the permissions on a symlink are ignored and the permission of the target are used)

as long as you don’t change any permissions on /var/run or on the docker.sock to be more permissive than they are now, there is functionally no difference in security 4.5) If you or someone else on the system tries to run docker with a different user/root, the symlink will likely cause issues
original
- Guadin@k.fe.derate.me ⁨11⁩ ⁨hours⁩ ago
  Thanks for the answer.
  
  Not really. I just never looked into podman and knew Docker already (as in, I can create container with docker compose).
  
  Running Patchmon in Docker does not work, it's the patchmon-agent to update the host running docker. So it needs access to apt on the host.
  
  Perfect, it shows as root but the user owns the original .sock.
  
  Will not do.
  
  Didn't think of that. Not a problem now but it could be in the feature.
  
  original
  - groet@feddit.org ⁨10⁩ ⁨hours⁩ ago
    Podman is pretty mutch a drop in replacement for docker but it runs in user context instead if root.
    
    All docker commands work with podman by just replacing the name including podman compose.
    
    (You do have to specify docker.io as a repository if you want to pull images from docker hub but that is literally the only difference In usage I ever noticed)
    
    original
Pika@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
I’m not fully understanding here, are you saying that the symlink is root because root is required to access /var/run or that its root because its required by patchmon.

If its root because the rest of the /var/run is root, is it not on the table to just chown the /var/run/docker.sock to be the userid? since I would assume that patchmon would be running as the docker user anyway since you are running in a rootless environment? I might be misunderstanding.

original
- Guadin@k.fe.derate.me ⁨11⁩ ⁨hours⁩ ago
  I tried to chown the /var/run/docker.sock but that doesn't work. It remains root, without errors.
  Patchmon runs as root, since the docker is on an other host an had the patchman agent. Patchmon needs to run as root since it uses apt to update.
  
  original
dan@upvote.au ⁨1⁩ ⁨day⁩ ago
Does Patchmon not have a setting to look for the Docker socket in a different location?

I could be wrong but I don’t think there’s any security issues making a symlink to a socket, since permissions/ACLs on the socket would still apply.

original
- Guadin@k.fe.derate.me ⁨1⁩ ⁨day⁩ ago
  No unfortunately they haven't implemented the option to point to a different docker.sock.
  
  original