Minikube 1.26.1 on WSLv2 Ubuntu 2204 ran in Podman Following Cgroup subsystem not mounted

[FilBot3]

What Happened?

When running minikube in WSLv2 Ubuntu 2204 with Podman, I am told I need to mount cgroup subsystem into the container. When running k0s, I had to mount a directory into the container for cgroupv2 --volume /sys/fs/cgroup:/sys/fs/cgroup:rw and setup --cgroupns=host. This allowed k0s to work.

Attach the log file

?  dudleyp
 minikube start --driver=podman
?  minikube v1.26.1 on Ubuntu 22.04
?  Using the podman driver based on existing profile
?  Starting control plane node minikube in cluster minikube
?  Pulling base image ...
E0830 14:12:25.619496   24540 cache.go:203] Error downloading kic artifacts:  not yet implemented, see issue #8426
?  Updating the running podman "minikube" container ...
?  Preparing Kubernetes v1.24.3 on CRI-O 1.24.1 ...
?  Problems detected in kubelet:
    Aug 30 19:13:32 minikube kubelet[23824]: E0830 19:13:32.031167   23824 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:33 minikube kubelet[23863]: E0830 19:13:33.039452   23863 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:34 minikube kubelet[23900]: E0830 19:13:34.043986   23900 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:35 minikube kubelet[23951]: E0830 19:13:35.067454   23951 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:36 minikube kubelet[24004]: E0830 19:13:36.033984   24004 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
?  Problems detected in kubelet:
    Aug 30 19:13:43 minikube kubelet[24431]: E0830 19:13:43.043798   24431 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:44 minikube kubelet[24476]: E0830 19:13:44.047663   24476 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:45 minikube kubelet[24525]: E0830 19:13:45.040206   24525 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:46 minikube kubelet[24560]: E0830 19:13:46.040291   24560 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
    Aug 30 19:13:47 minikube kubelet[24606]: E0830 19:13:47.042206   24606 kubelet.go:1378] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"

Operating System

• Ubuntu 2204 via WSLv2 on Windows 10

Driver

• Podman

[fireinrain]

it seems problem is wsl2 on windows

[RA489]

/kind support

[rodriguezc]

Hi,
I have the same issue.
Environment:

• Windows 10
• WSL2
• Ubuntu 22.04
• Podman 3.4.4

minikube start  --embed-certs
...
W1209 17:01:04.354308   68908 logs.go:138] Found kubelet problem: Dec 09 16:00:57 minikube kubelet[18147]: E1209 16:00:57.561504   18147 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
W1209 17:01:04.361586   68908 logs.go:138] Found kubelet problem: Dec 09 16:00:58 minikube kubelet[18226]: E1209 16:00:58.737930   18226 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
W1209 17:01:04.368349   68908 logs.go:138] Found kubelet problem: Dec 09 16:00:59 minikube kubelet[18300]: E1209 16:00:59.666751   18300 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
W1209 17:01:04.375285   68908 logs.go:138] Found kubelet problem: Dec 09 16:01:00 minikube kubelet[18361]: E1209 

16:01:00.740875   18361 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
W1209 17:01:04.382631   68908 logs.go:138] Found kubelet problem: Dec 09 16:01:01 minikube kubelet[18440]: E1209 16:01:01.947821   18440 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
W1209 17:01:04.387891   68908 logs.go:138] Found kubelet problem: Dec 09 16:01:02 minikube kubelet[18501]: E1209 16:01:02.951853   18501 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
W1209 17:01:04.396784   68908 logs.go:138] Found kubelet problem: Dec 09 16:01:04 minikube kubelet[18565]: E1209 16:01:04.262965   18565 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"

I1209 17:01:04.546038   68908 out.go:177] ❌  Problems detected in kubelet:
I1209 17:01:04.550027   68908 out.go:177]     Dec 09 16:00:57 minikube kubelet[18147]: E1209 16:00:57.561504   18147 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
I1209 17:01:04.557438   68908 out.go:177]     Dec 09 16:00:58 minikube kubelet[18226]: E1209 16:00:58.737930   18226 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
I1209 17:01:04.562349   68908 out.go:177]     Dec 09 16:00:59 minikube kubelet[18300]: E1209 16:00:59.666751   18300 kubelet.go:1397] "Failed to start ContainerManager" err="system validation failed - Following Cgroup subsystem not mounted: [cpuacct]"
I1209 17:01:04.568044   68908 out.go:177] 
W1209 17:01:04.571230   68908 out.go:239] ❌  Exiting due to K8S_KUBELET_NOT_RUNNING: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.25.3:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 1

@FilBot3 Can you give more details about your solution? Commands to execute. Thanks!

[rodriguezc]

Seems to be related with this issue in fact : microsoft/WSL#6662

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.