5 ms·
The most common one I run into is with volumes, when the full path doesn't already exist. Docker will just make the path, Podman throws an error. It's been call
by enlightens 7mo ago
The most common one I run into is with volumes, when the full path doesn't already exist. Docker will just make the path, Podman throws an error. It's been called a "bug" in docker but the fact is everyone just expects the paths to be created. I want it to just work, not make everyone in the industry redo their dockerfiles to be "correct."
https://github.com/containers/podman/issues/6234 https://github.com/containers/podman/issues/6234
It looks like there was some work done to resolve this in 2023 and 2024 but I know this was still happening for me in mid 2025. Podman is technically correct here but functionally broken in a way that keeps pushing me away because I don't have time to deal with that :(
- lukeschlather 7mo agoRunning a docker container having side effects on the host seems bad. You've just convinced me a little bit I want podman, and not docker.
- newsoftheday 7mo agoNot me, docker is the standard, works great for me, if it didn't, I'd look at alternatives.
- dizhn 7mo agoPodman also works great but one has to stop trying to use it as if it were docker.