4 ms·
I'm probably just missing some fundamental knowledge, but why does podman need it's own network stack? Doesn't linux include functionality for things like virtu
by SahAssar 5y ago
I'm probably just missing some fundamental knowledge, but why does podman need it's own network stack? Doesn't linux include functionality for things like virtual networks, bridges, virtual networks and similar?
EDIT: the second "virtual networks" meant to say "virtual interfaces"
- metadat 5y agoOut-of-the-box Linux doesn't handle container networking in a default fashion, because there are many common configurations and techniques available to obtain different effects and results for the exact nature of each network being attached or created.
- freedomben 5y agoWhen they say "network stack" they don't mean their own implementations of TCP and UDP like you would for an OS (like linux). They mean the various pieces that the container runtime has to implement. See CNI[1] for more information. [1]: https://www.cni.dev/ https://www.cni.dev/
- SahAssar 5y agoSo it's the "compiler" for a CNI spec into a configuration for a linux network namespace?
- freedomben 5y agoYeah I think that's a reasonable way to think of it. When a container (or Pod) gets created it needs a handful of network stuff setup, from creating the virtual network interfaces, setting up route tables. nftables/iptables rules, assigning an IP address, setting up NAT, configuring container-to-container networking, etc.
- SahAssar 5y agoThanks, that makes sense. I'd prefer it'd be called something else than a "network stack", but that's life.