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.

  • Justin@lemmy.jlh.name
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    7 months ago

    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.

    • CronyAkatsukiOPA
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      I have been thinking about moving to kubernetes, this just adds gives me another notch into doing it.

      • Justin@lemmy.jlh.name
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        Yeah, there’s definitely a learning curve since it’s so different from docker, but there are some good tutorials and everything just makes sense. All the error messages are googlable and everything fits together so well.