From what I have seen, rootless podman seems to take more effort (even if marginal) than rootful one. I want to make a more informed decision for the containers, so I would like to ask.

  1. What is a rootless podman good for? How much does it help in terms of security, and does it have other benefits?
  2. One of the benefits commonly mentioned is for when container is breached. Then, running container on sudo-capable user would give no security benefits. Does it mean I should run podman services on a non-privileged user?

Thank you!

  • asap@lemmy.worldEnglish
    1·
    1 day ago

    You need to add :Z to the end of your volume lines, or lowercase z for shared volumes.

    I’m running 50+ containers, probably most of the popular ones, and all working fine.

    • Railcar8095@lemm.eeEnglish
      1·
      9 hours ago

      You made me try again, and I again failed. For example, Navidrome has this issue: https://github.com/navidrome/navidrome/issues/2967

      It seems aside from :z i have to remap the user namespace, which I remember trying in the past too and getting mixed results (some worked, some still didn’t). I get this is not a podman issue (also affects rootless docker), but given the default behavior of docker is root, I am not having this issue.

      The others didn’t seem to fail at creation, which is a good thing, but I recall some had issues interacting with each other (files created by one not being readable by another and such). Might try with some other navidrome image (or equivalent subsonic server) but unless it’s as easy as adding :z, I don’t think ill be able to continue Thanks in any case :)

      • asap@lemmy.worldEnglish
        1·
        3 hours ago

        Here’s my Navidrome config. This is running on uCore version of CoreOS, with rootless Podman and SELinux. I made no configuration changes to Podman out-of-the-box, and this is the full compose file.

        i have to remap the user namespace

        Note: I have not done this. What are you running Podman on? Perhaps there is some config issue with the host, since you’re having issues with many containers?

        To be fair, maybe just go with docker if it’s causing that much pain. But again, mine is working OOTB without making any changes to the Podman setup on ucore, and using the config below.

        services:
  navidrome:
    image: deluan/navidrome:latest
    container_name: navidrome
    ports:
      - "3015:4533"
    restart: unless-stopped
    environment:
      # Optional: put your config options customization here. Examples:
    volumes:
      - ./data:/data:Z
      - ./config.toml:/navidrome.toml:Z
    • felbane@lemmy.worldEnglish
      1·
      18 hours ago

      I don’t necessarily agree with it, but there’s the third option of just disabling SELinux and removing the frustration entirely.