Signed-off-by: Maël Valais <[email protected]>

In this PR, I added a CNI configuration so that containerd stops
complaining about not being able to load the CNI plugin. The message
was:

  failed to load cni during init, please check CRI plugin status before
  setting up network for pods  error="cni config load failed: no network
  config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config"

The cni.json file is picked up by nerdctl as a network:

  root@8deca99e60b5:/# nerdctl network ls
  NETWORK ID    NAME      FILE
                bridge    /etc/cni/net.d/nerdctl-bridge.conflist
                host
                none

It is important to use the name "bridge" in the CNI configuration, ie.,
you should see:

  {
    "cniVersion": "1.0.0",
    "name": "bridge",
    ...
  }

Otherwise, nerdctl will try to create another bridge network, and you
will get the following error message:

  FATA[0002] failed to create default network: subnet 10.4.0.0/24 overlaps with other
  one on this address space

The following warning can be ignored:

  WARN[0002] default network named "bridge" does not have an internal nerdctl ID or
  nerdctl-managed config file, it was most likely NOT created by nerdctl

Signed-off-by: Maël Valais <[email protected]>