Comment # 5 on bug 1140067 from Sascha Grunert

(In reply to Marco Vedovati from comment #4)
> (In reply to Richard Brown from comment #3)
> > If you do that you won���t ever be able to install podman on a machine with a
> > custom chi config, such as one using cri-o/kubernetes 
> > 
> > That seems silly, given one of the use cases for podman is troubleshooting
> > containers on systems with cri-o/kubernetes
> 
> Sascha WDYT?

I think we could change the libpod.conf to comment out `cni_default_network`.
Then podman should select the config with the highest priority in
`cni_plugin_dir`. Then we could make podman-cni-config mandatory, because user
would still be able to put higher prio configs in.