Start minikube on Windows: OCI runtime error

kubernetes / minikube

Run Kubernetes locally

https://minikube.sigs.k8s.io/

Apache License 2.0

28.72k stars 4.81k forks source link

Start minikube on Windows: OCI runtime error #17917

Open tschroe opened 5 months ago

tschroe commented 5 months ago

What Happened?

I've been using Podman and Podman Desktop for a while now. Now I've tried to install Minikube using

minikube start --driver=podman --container-runtime=cri-o

But I always got error messages, like this one

Error: unable to start container "4ba458f0985470022704ade69a764fdcc1c163801e77e8512b51058592bf9bee": crun: chmod run/shm: Operation not supported: OCI runtime error

I've tried updating Podman and Podman Desktop, first downloading minikube and then starting, running minikube delete before the start, rootless and rootful Podman, different container-runtimes and drivers, and honestly I spent a lot of time trying to get rid of this message Error downloading kic artifacts: not yet implemented, see issue https://github.com/kubernetes/minikube/issues/8426

I can't get it to work, the new container has never started on my machine. Can you please give me a hint?

Attach the log file

logs.txt

Operating System

Windows

Driver

Podman

k8s-triage-robot commented 2 months ago

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

havryliuk commented 1 month ago

Getting the same issue on Windows 11 when running minikube start --cpus 2 --memory 2000 --driver=podman.

Error: unable to start container "ff982549459f13eedb5ff00b29b7204649901d9908539d9aa0827c5455735692": crun: chmodrun/shm: Operation not supported: OCI runtime error

k8s-triage-robot commented 3 weeks ago

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