containers
/
automation-tests
mirror of https://github.com/containers/automation-tests.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #10346 from Luap99/network-doc 

[CI:DOCS] network tutorial: update with rootless cni changes
This commit is contained in:
OpenShift Merge Robot 2021-05-16 07:02:17 -04:00 committed by GitHub
parent 90a12acb7e 460182dc5d
commit a6a3df0273
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/tutorials/basic_networking.md
View File

@ -87,12 +87,16 @@ network, and the one will be created as a bridge network.
$ podman network create $ podman network create
``` ```
When rootless containers are run with a CNI networking configuration, a “side-car” When rootless containers are run with a CNI networking configuration, CNI operations
container for running CNI is also run. Do not remove this container while your rootless will be executed inside an extra network namespace. To join this namespace, use
containers are running. if you remove this container (e.g by accident) all attached `podman unshare --rootless-cni`. Podman version 3.1 and earlier use a special “side-car”
containers lose network connectivity. In order to restore the network connectivity container called rootless-cni-infra. Do not remove this container while your rootless
all containers with networks must be restarted. This will automatically recreate containers are running. If you remove this container (e.g. by accident), all attached
the "side-car" container. For rootfull containers, there is no “side-car” container containers lose network connectivity. In order to restore the network connectivity, all
containers with networks must be restarted. This will automatically recreate the "side-car"
container. When you are using version 3.2 or newer the “side-car” container can be
safely removed. Therefore, it is no longer used.
For rootfull containers, there is no extra namespace or “side-car” container
as rootfull users have the permissions to create and modify network interfaces on as rootfull users have the permissions to create and modify network interfaces on
the host. the host.