I’m moving to a new machine soon and want to re-evaluate some security practices while I’m doing it. My current server is debian with all apps containerized in docker with root. I’d like to harden some stuff, especially vaultwarden but I’m concerned about transitioning to podman while using complex docker setups like nextcloud-aio. Do you have experience hardening your containers by switching? Is it worth it? How long is a piece of string?

  • herrfrutti@lemmy.worldEnglish
    0·
    2 months ago

    I’m running podman and podman-compose with no problem. And I’m happy. At first I was confused by the uid and gid mapping the containers have, but you’ll get used to it.

    This are some notes I took, please don’t take all of it for the right choice.

    Podman-Stuff

    https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md

    storage.conf

    To use the fuse-overlay driver, the storage must be configured:

    .config/containers/storage.conf

    [storage]
  driver = "overlay"
  runroot = "/run/user/1000"
  graphroot = "/home/<user>/.local/share/containers/storage"
  [storage.options]
    mount_program = "/usr/bin/fuse-overlayfs"

    Lingering (running services without login / after logout)

    https://github.com/containers/podman/issues/12001

    https://unix.stackexchange.com/questions/462845/how-to-apply-lingering-immedeately#462867

    sudo loginctl enable-linger <user>
    • bigdickdonkey@lemmy.caOPEnglish
      0·
      2 months ago

      Do you need to set lingering for all container users you set up? Does it restart all services in your compose files without issue?

      • herrfrutti@lemmy.worldEnglish
        1·
        2 months ago

        Yes all users that have containers running, that should keep running need lingering.

        The Services do not restart themself. I have cronjob that executes podman start --all at reboot for my “podman user”.

  • K3CAN@lemmy.radioEnglish
    0·
    2 months ago

    I use podman almost exclusively at this point. I like having the rootless containers and secrets management. If you’re on Debian, though, I strongly suggest pulling podman from Trixie. The version in Bookworm is very out of date and there’s been a lot of fixes since then.

    • lambalicious@lemmy.sdf.orgEnglish
      1·
      2 days ago

      , I strongly suggest pulling podman from Trixie

      Question since I try to use backports and stuff where possible: Is trixie more advisable than pulling from sid for stuff like this?