3 ms·
I mentioned this in other comment here but it's relevant here too Podman: - does not mess with your iptables unlike docker. Because of this docker containers
by anthropodie 5y ago
I mentioned this in other comment here but it's relevant here too
Podman:
- does not mess with your iptables unlike docker. Because of this docker containers can bypass firewall rules set by ufw
- does not creates bridged networks
- remram 5y agoApologies for the possibly dumb question, I couldn't find this in the Podman docs. How does it do networking without bridges? Does it still use veth devices?
- anthropodie 5y agoThat's a valid question. I also did not look up until you asked. Check this out[1] > One of the guiding factors on networking for containers with Podman is going to be whether or not the container is run by a root user or not. This is because unprivileged users cannot create networking interfaces on the host. Therefore, with rootfull containers, the default networking mode is to use netavark. For rootless, the default network mode is slirp4netns. Because of the limited privileges, slirp4netns lacks some of the features of networking; for example, slirp4netns cannot give containers a routable IP address. [1]: https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md https://github.com/containers/podman/blob/main/docs/tutorial...
- remram 5y agoThanks! It seems that netavark uses macvlan to avoid creating bridge devices. Although it can also use bridges, and Docker added macvlan support too: https://github.com/moby/libnetwork/blob/master/docs/macvlan.md https://github.com/moby/libnetwork/blob/master/docs/macvlan.... That page also gives a lot of background on the different methods and their pros/cons. I guess at this point the difference is only the defaults of each system.