podman/cni
Brent Baude cfd4060890 add firewall plugin (no backend) to default cni config
in order for the fall back mechanisms to work in containernetworking-plugins, the firewall plugin must still be called via the cni configuration file.  however, no backend will be specified as we will rely on cni to do the right thing.

Signed-off-by: Brent Baude <bbaude@redhat.com>
2020-02-27 14:35:48 -06:00
..
87-podman-bridge.conflist add firewall plugin (no backend) to default cni config 2020-02-27 14:35:48 -06:00
README.md Update cni config instructions 2019-08-22 19:39:07 -04:00

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).

For example a basic network configuration can be achieved with:

sudo mkdir -p /etc/cni/net.d
curl -qsSL https://raw.githubusercontent.com/containers/libpod/master/cni/87-podman-bridge.conflist | sudo tee /etc/cni/net.d/87-podman-bridge.conf

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 libpod.conf). Please refer to the CNI project page in GitHub for more information.