108d2bc430
The docs were rather vague about the deprecation of CNI, make it clear that we are going to remove it with 5.0 as we decided to do that in our planning. Also while looking at the podman network create docs I noticed --ipam-driver dhcp was still documented as not supported with netavark so I fixed that as well. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
cni
Note: The CNI backend is deprecated and will be removed in the next major Podman version 5.0, in preference of Netavark, see podman-network(1) on how to change the backend.
There are a wide variety of different CNI network configurations. This directory just contains an example configuration that can be used as the basis for your own configuration.
To use this configuration, place it in /etc/cni/net.d (or the directory
specified by cni_config_dir in your containers.conf).
For example a basic network configuration can be achieved with:
sudo mkdir -p /etc/cni/net.d
curl -qsSL https://raw.githubusercontent.com/containers/podman/main/cni/87-podman-bridge.conflist | sudo tee /etc/cni/net.d/87-podman-bridge.conflist
Dependent upon your CNI configuration, you will need to install as a minimum the port and bridge CNI plugins into /opt/cni/bin (or the directory specified by cni_plugin_dir in containers.conf). Please refer to the CNI project page in GitHub for more information.