3 ms·
> The underlying runtime leaks through For those of us who have never used Podman or explored the depths of Docker, can you explain what you mean by that?
by foresto 5y ago
> The underlying runtime leaks through
For those of us who have never used Podman or explored the depths of Docker, can you explain what you mean by that?
- Macha 5y agoA recent example > $ podman start my_container > sd-bus call: Permission denied: OCI runtime permission denied error What on earth is an on OCI runtime? How are its permissions configured? Here's some issues with some random flags to configure: https://github.com/containers/podman/issues/6368 https://github.com/containers/podman/issues/6368 . How are these linked to podman? The devs know, where is this documented for Joe random user? Or another one I ran into: https://github.com/containers/podman/issues/7830 https://github.com/containers/podman/issues/7830 Again, here's some settings in files in /etc/containers to configure that might fix it? Where is this in the podman docs, or release notes? Just found my pods didn't start after an update one day and had to dig into github issues.
- foresto 5y agoI see. So the criticism here is that Podman's error reporting is sometimes insufficient to explain an error triggered by systemd/cgroup changes. Docker has the same (class of) problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992486 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992486 It is indeed frustrating. I don't think I'll count it as a reason to avoid Podman, though, since Docker is no better.