Comment 14 for bug 2024394

From what I can tell, any networks I had running with CNI version 0.4.0 were running fine, even after podman updated to 3.4.4. I only had the issue when I created a new interfaces while running podman 3.4.4, at which point the configuration for those new network interfaces were trying to use CNI version 1.0.0 instead of 0.4.0.

To resolve this, instead of downgrading the podman version (or upgrading podman from a different repo), I simply changed the CNI version being used by the network I created. I did this by manually editing the .conflist file in the ~/.config/cni/net.d/ directory for the network I had created, changing the "cniVersion" field from "1.0.0" to "0.4.0".

Once I did this, everything seemed to work for me and I no longer had the error messages appearing.

Since it doesn't involve changing the installed podman version or any of the other installed packages, this should be a workaround that works with ARM processor.

Hope that helps..