3 ms·

I'm genuinely curious here. I've literally never run into anything that required the rootful daemon. What exactly are people relying on that requires that?

• Fire-Dragon-DoL 3y ago
  Expose port 443 (yes, for https). i know there are workarounds, just saying it is not a drop-in. I decided to run an app in docker rootless in my personal server and there are a whole bunch of problems related to that. A lot of images expect to be run as "root all the way down"
• bravetraveler 3y ago
  Most common/immediate example: mounting volumes to files they normally can't interact with. As a normal, non-root user, that is! One may need to account for permissions and ownerships more when using podman compared to Docker. Being in the 'docker' group allows the daemon to set the stage for you. Many ways to address it. For example, using named volumes instead of mounts. ... but a lot of people use mounts expecting something different than what podman offers, due to permissions/ownerships; it is notable
  • zaphar 3y ago
    Wow, that seems like using Docker wrong. But I guess if you got used to abusing it like that then not being able to do so is gonna hurt a bit.
    • bravetraveler 3y ago
      Eh, it's an alright use for Docker. I get not using named volumes - easy to forget they exist. It's tough for me to point 'blame' any which way, both models are fine enough. UID/GID stuff can get messy fast, I prefer podman/'seeing the warts'