mirror of
https://github.com/containers/podman.git
synced 2025-05-17 23:26:08 +08:00
Merge pull request #14688 from rhatdan/docs
[CI:DOCS] Update basic_networking.md
This commit is contained in:
@ -13,13 +13,14 @@ Each setup is supported with an example.
|
|||||||
|
|
||||||
## Differences between rootful and rootless container networking
|
## Differences between rootful and rootless container networking
|
||||||
|
|
||||||
One of the guiding factors on networking for containers with Podman is going to be
|
One of the guiding factors on networking for containers with Podman is going to
|
||||||
whether or not the container is run by a root user or not. This is because unprivileged
|
be whether or not the container is run by a root user or not. This is because
|
||||||
users cannot create networking interfaces on the host. Therefore, with rootful
|
unprivileged users cannot create networking interfaces on the host. Therefore,
|
||||||
containers, the default networking mode is to use netavark.
|
for rootless containers, the default network mode is slirp4netns. Because of the
|
||||||
For rootless, the default network
|
limited privileges, slirp4netns lacks some of the features of networking
|
||||||
mode is slirp4netns. Because of the limited privileges, slirp4netns lacks some of
|
compared to rootful Podman's networking; for example, slirp4netns cannot give
|
||||||
the features of networking; for example, slirp4netns cannot give containers a
|
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.
|
routable IP address.
|
||||||
|
|
||||||
## Firewalls
|
## Firewalls
|
||||||
|
Reference in New Issue
Block a user