Thanks for the answer.

1. Not really. I just never looked into podman and knew Docker already (as in, I can create container with docker compose).
2. 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.
3. Perfect, it shows as root but the user owns the original .sock.
4. Will not do.
5. Didn’t think of that. Not a problem now but it could be in the feature.

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.

No unfortunately they haven’t implemented the option to point to a different docker.sock.