On 07/05/2023 08:34, Taro Yokoyama wrote:
Hi Lejeczek,
It seems that the behavior is similar to this
ticket(https://github.com/containers/podman/issues/13396).
my assuming is that system resets setting by performing
‘podman system reset’ command and it looks like setup with
CNI warns due to not utilizing containernetworking-plugins
and netavark setting is internally selected by ‘podman
network ls’ command at the first attempt after the reset,
which of status is cached.
Best Regards,
Taro
2023年5月6日(土) 18:31 lejeczek via Podman
<podman(a)lists.podman.io>:
Hi guys.
I'm seeing something strange and I hoped experts/devel
would comment, on:
-> $ podman network ls
NETWORK ID NAME DRIVER
2f259bab93aa podman bridge
-> $ podman system reset --force
-> $ podman network ls
WARN[0000] Error validating CNI config file
/etc/cni/net.d/87-podman-bridge.conflist: [failed to
find plugin "bridge" in path [/usr/local/libexec/cni
/usr/libexec/cni /usr/local/lib/cni /usr/lib/cni
/opt/cni/bin] failed to find plugin "portmap" in path
[/usr/local/libexec/cni /usr/libexec/cni
/usr/local/lib/cni /usr/lib/cni /opt/cni/bin] failed
to find plugin "firewall" in path
[/usr/local/libexec/cni /usr/libexec/cni
/usr/local/lib/cni /usr/lib/cni /opt/cni/bin] failed
to find plugin "tuning" in path
[/usr/local/libexec/cni /usr/libexec/cni
/usr/local/lib/cni /usr/lib/cni /opt/cni/bin]]
NETWORK ID NAME DRIVER
2f259bab93aa podman bridge
then I ssh-log out & in, things seem okey:
-> $ podman network ls
NETWORK ID NAME DRIVER
2f259bab93aa podman bridge
and if I 'reset' then in circles it goes.
what is actually happening here?
Is system setup/installation missing something?
many thanks, L.
It seems that this: /etc/cni/net.d/87-podman.conflist is
some remainer of some previous installation, previous version?
On a few different systems where the same version of podman
is installed that file does not exist and 'system reset'
does not seem to care about the file.
Also '/etc/udev/rules.d/etc/cni/net.d/87-podman.conflist'
existed - past tense as I removed both and now 'system
reset' and subsequent operations do not complain about that,
no log out&in necessary.
thanks, L.