mirror of
https://github.com/containers/podman.git
synced 2025-06-20 00:51:16 +08:00
Update basic_networking.md
a little enhancement based on the [comment by @TomSweeneyRedHat](https://github.com/containers/podman/pull/14290#pullrequestreview-979316099) Replaces: https://github.com/containers/podman/pull/14290 Thanks to @vrms Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
@ -13,13 +13,14 @@ Each setup is supported with an example.
|
||||
|
||||
## Differences between rootful and rootless container networking
|
||||
|
||||
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 rootful
|
||||
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
|
||||
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,
|
||||
for rootless containers, the default network mode is slirp4netns. Because of the
|
||||
limited privileges, slirp4netns lacks some of the features of networking
|
||||
compared to rootful Podman's networking; for example, slirp4netns cannot give
|
||||
containers a routable IP address. The default networking mode for rootful
|
||||
containers on the other side is netavark, which allows a container to have a
|
||||
routable IP address.
|
||||
|
||||
## Firewalls
|
||||
|
Reference in New Issue
Block a user