I think you can send a SIGUSR1 signal to mumble process to tell it to reload the ssl certificate without actually restarting mumble's process. You can use docker kill --signal="SIGUSR1" <container name or id>, but then you still need to give your user access to docker group. Maybe you can setup a monthly cron on root user to run that command every months?

Create a sudo rule which allows the user to run only this exact command: "sudo docker restart mycontainer"

Looks like you can create a simple binary executable and make it run as root with setuid.

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

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

Did you think about automating the certificate generation? You could put everything into a cron script. That's more or less the reason why certificates have such a short lifetime. To force automation.

Not sure how your stack works together, but sudo will let you run particular commands as a different user and you can be pretty specific with the privileges. For example you can have a script that’s only allowed to run docker compose -f /path/to/compose.yml restart containername as a user in the docker group. Maybe there’s some docker-specific approach, but this should work with traditional Unix tools and a little scripting.

Kubernetes has user accounts that you could use to restart containers in an unprivileged way. Create a role and role binding that gives the "delete Pod" permission to a service account. Kind makes it very easy to run Kubernetes without any setup. You'd just need to convert your docker compose files to Deployments, Services, and PersistentVolumes.

If converting to a kubernetes setup is too big of a leap, you could maybe try to write a C program that uses setuid to gain docker privileges in a restricted way.

Probably easiest to just have a cronjob that restarts the container regularly, though.

If a user is in the docker group they can also run docker commands.