Re: [meta-virtualization][PATCH] netavark: init at 1.1.0

[Embedded Devel <yocto@optimcloud.com>]

On Thursday 18 August 2022 20:45:42 PM (+07:00), Bruce Ashfield wrote:

 > On Thu, Aug 18, 2022 at 9:17 AM Bach, Pascal <pascal.bach@siemens.com> 
wrote:
 > >
 > > > >
 > > > > Netavark is replaces cni for podman.
 > > > >
 > > >
 > > > s/is replaces/is a replacement/
 > > >
 > > > Since this can replace CNI, can they co-exist at the same time ? We 
should
 > > > mention that in the commit message. If they both can't be active on 
the
 > > > target at the same time, then we should have a RCONFLICTS in the 
recipe to
 > > > make sure they aren't both installed.
 > > >
 > >
 > > Both can be installed in parallel. And from what I have seen if both 
are installed
 > > podman seems to prefer netavark.

They can be installed together and should, netavark is and will be the 
primary, and you must configure manually to use cni
yet CNI and Netavark cannot be used simultaneously in order to avoid 
conflicts in the configurations the two create.

 >
 > likewise, that is what I was seeing as well. But I've been avoiding it
 > (netavark) for CNI so far :)
 >
 > > The backend can be mahually selected in the podman config
 > > 
https://github.com/containers/common/blob/main/docs/containers.conf.5.md#network-table
 
> > but only one can be used at a time.
 >
 > I can run my multi-container, multi-runtime tests against it at some
 > point (I put all the runtimes, all the frameworks and all the
 > networking on a single image to see what breaks), and then document
 > the results.
 >
 > Bruce
 >
 > >
 > > Pascal
 >
 >
 >

-- 
Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com