this post was submitted on 26 Jun 2026
23 points (100.0% liked)
Selfhosted
60451 readers
639 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If it's running as root anyway, then I change my statement. No I don't see any security risk with it. Patchmon is running as root anyway, so no matter what your permissions are on the links or the original sock, as long as it's smart enough to follow the link it should be fine. Generally symlinks follow the same permission as their target, with the exception of changing its owner with chown or removing it. I.E they are going to almost always just be whatever the permission of the target is. So your /var/run/docker.sock is going to be whatever permissions your /run/user/{userid}/docker.sock is normally and since patchmon is running as the root user, it's not going to care what permissions are present as root overrides all restrictions/permissions anyway.
I have my concerns that patchmon might try to change docker files while as the root user, which could create files that docker couldn't read but since it seems to be using the docker sock anyway, I expect it's just going to operate over the sock which means it would be using dockers built in system which would be using its docker user.