Could we enable back cni BUILDTAG?

[dennybaa]

Hello, 5x with netavark has issues when running on cloud environments such as GKE, AWS. However 4.9.5 is working well because it opts in for CNI backend, why couldn't we have both complied in?

[dennybaa]

There is no known way to overcome this error, unfortunately(

netavark: Sysctl error: IO Error: Read-only file system (os error 30))

[mgoltzsche]

As far as I am aware support for the CNI network stack has been deprecated within podman 4 and was removed within podman 5.0 (see here).
Can you point me to an issue within the upstream podman project that discusses those network problems within cloud environments?

[dennybaa]

@mgoltzsche It's deprecated, but it wasn't removed, it's available as a feature flag. I had to enable it back in my fork. I think doesn't bother if it's compiled in https://github.com/bitdeps/podman-static/blob/124685ca7e7ec9857a59fcf9f9539b01e38956a0/Dockerfile#L31

[dennybaa]

Sure here's the issue containers/netavark#825

[mgoltzsche]

Thanks for linking the upstream podman issue.
I'd expect the upstream podman project to solve that but, given that their issue is very old and you say podman is still working with CNI, I am inclined to accept a PR that enables CNI support within this repo again for the time being. In that case I think it would be good to add CNI plugins only to the regular, non-minimal image but omit them within the minimal image to keep the latter minimal as the name suggests.

[mgoltzsche]

Or even better: publish a CNI image variant under a separate tag, e.g. 5.4.0-cni.