mirror of
https://github.com/containers/podman
synced 2024-10-19 08:44:11 +00:00
7b4102ce28
Both Podman and CRI-O set up CNI bridges with the name 'cni0'. If both our CNI conflist and the CRI-O conflist are installed, whoever runs first will win - that is, they will configure the bridge, and everyone will use it. Problem: the CRI-O CNI config conflicts with ours and results in containers with no networking. Solution: rename our bridge so we don't conflict with CRI-O. At the same time, hit our IPAM configuration. The current version was an older format in danger of deprecation. The new format is documented at [1]. Finally, fix indentation for the entire file. [1] https://github.com/containernetworking/plugins/tree/master/plugins/ipam/host-local#example-configurations Signed-off-by: Matthew Heon <matthew.heon@pm.me> |
||
---|---|---|
.. | ||
87-podman-bridge.conflist | ||
README.md |
cni
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 libpod.conf
).
In addition, you need to install the CNI plugins necessary into
/opt/cni/bin
(or the directory specified by cni_plugin_dir
). The
two plugins necessary for the example CNI configurations are portmap
and
bridge
.