FS#75219 - [minikube] include the 'cni-plugins' as dependency when used with the 'podman' VM-driver
Attached to Project:
Community Packages
Opened by Sebastian Makowiecki (muthuh) - Sunday, 03 July 2022, 11:25 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:04 GMT
Opened by Sebastian Makowiecki (muthuh) - Sunday, 03 July 2022, 11:25 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:04 GMT
|
Details
Description:
=========== Starting 'minikube' (`minikube start`) with the 'podman' VM-driver results in an ------ "Error: netavark: failed to configure bridge and veth interface: failed while configuring network interface: failed to create a bridge interface podman0: Received a netlink error message Operation not supported (os error 95)'" ------ error, unless the package 'cni-plugins' is installed. It might be worthwhile to include in the suggested list of 'minikube' dependencies. Additional info: =============== * package version(s) minikube 1.25.2-1 podman 4.1.1-2 cni-plugins 1.1.1-2 * a similar issue that led me to the missing dependency: https://github.com/containernetworking/cni/issues/770 Steps to reproduce: ================== Install the 'minikube' and 'podman' (no docker on the system) and initialize the minikube environment with the `minikube start` command. |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:04 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/minikube/issues/1
Saturday, 25 November 2023, 20:04 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/minikube/issues/1
With no 'fuse-overlayfs' installed the 'minikube start' run fails with: "podman: Not healthy: "sudo -n -k podman version --format {{.Version}}" exit status 125: Error: kernel does not support overlay fs: 'overlay' is not supported over extfs at "/var/lib/containers/storage/overlay": backing file system is unsupported for this graph driver"
The 'fuse-overlayfs' is not mentioned on neither 'podman' nor 'minikube' (optional) dependencies.
'podman' is not mentioned on the list of optional 'minikube' deps at all.
A quick StackExchange visit later (https://unix.stackexchange.com/a/689182/100189) and got the 'fuse-overlayfs' installed, only to encounter the error reported originally, so I'm back.
Additionally let me just mention that it is pretty much normal procedure to run the 'minikube start' to get it going. When these additional bits are not present it is guaranteed not to succeed - therefore I ask: is this sort of situation with the (no doubt optional) dependencies not allowing to make use of a package the very definition of the optional-dependencies of a package?
Thanks a lot for looking into it, much appreciate. Perhaps worth considering the fact these packages do indeed form an ecosystem of interlinked dependencies, granted - depending on a use-case. Cheers.
Podman itself now relies on netavark by default (via containers-common), but AFAIK it can still make use of cni-plugins (it's just discouraged by upstream).
@shibumi: I believe it would be very good to add cni-plugins as optional dependency at least.