Selfhosted

40438 readers

448 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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 2 years ago

MODERATORS

[email protected]

Restart Docker Container Without root privileges (lemmy.cronyakatsuki.xyz)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

Hello, I have a mumble server running as a docker container.

I'm using lego to generate let's encrypt certificates using dns challenge as an unprivileged user.

My problem is that I need to restart the mumble server so that it can reload the ssl certificate, which means restarting the docker container.

Is there any way to do this withuot adding the user to docker group, since there are security issues with that group where it's easy to escalate to a root user.

I thought about maybe a user level systemd service could be able to do it, but wan't to hear your opinions?

EDIT: I mention mumble specifically here, but this can apply to any server that requires manual reload of ssl keys, like postfix for example. I'm also not againd the idea of converting to something like kubernetes or even podman ( which would be harder cause of file permissions on all my binds ) if they can allow for woking on the container without root privileges.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago) (1 children)

You could write a script that just restarts your container, make sure unprivileged users cannot edit it, and do one of two things:

make a sudoers entry for your unprivileged account to call just that script as a user in the docker group with sudo
use setuid on the script to have it execute from the docker group even when executed by users

[–] ShawiniganHandshake 3 points 7 months ago

Most shells ignore setuid on scripts for security reasons.