my understanding was that it was docker that doesnt need root or a daemon.
i always thought it seemed wrong that it needed either of those to start with.
in most other respects i think it's a drop in replacement.
i always thought it seemed wrong that it needed either of those to start with.
in most other respects i think it's a drop in replacement.
- does not mess with your iptables unlike docker. Because of this docker can bypass firewall rules set by ufw
- does not creates bridged networks
If you are running kubernetes there are k8s daemons already possibly CRI-O containerd Otherwise the pod is started by systemd, which is another daemon
A Started from the command line using podman, is not a production pattern
There are also a bunch of tools that talk directly to the docker socket.
There are a lot of varying use cases here.
Disclaimer, I started Rancher Desktop.
Totally makes sense when you understand more but initial is surprising.
1. It can form up k8s-style pods for deploying tightly-coupled containers. 2. It can understand k8s YAML for deployment (although obviously it doesn't support everything k8s does), which makes it easier to do deployment config that will work locally with podman and then in a k8s deployment.