Not able to run Minikube using Podman

[Reehansz]

What Happened?

I was trying to install Minikube in Mac M3 arm, when trying to install it using "Minikube start --driver Podman", I was not able to install it due the below error

Attach the log file

❌ Exiting due to GUEST_STATUS: Unable to get control-plane node minikube host status: state: unknown state "minikube": podman container inspect minikube --format={{.State.Status}}: exit status 125
stdout:

stderr:
Error: no such container "minikube"

Operating System

macOS (Default)

Driver

Podman

[pingora-gateway]

what is your podman version?

[Reehansz]

podman version 5.3.2

[dhairya-seth]

I had also faced the same issue when starting minikube using Podman driver. To start minikube i had to reset the minikube configurations and restarted it using Docker driver. It was working properly using docker.

[dhairya-seth]

If (in case) you want to run minikube using docker, you can follow the steps mentioned below, which worked for me:

1. If you executed these commands: minikube config set driver podman and minikube config set rootless true in past while setting up podman then you need to unset it using minikube config unset driver and minikube config unset rootless.
2. Install docker (if not installed) and ensure docker engine is in running state.
3. Then start minikube using minikube start --driver=docker
4. If you still get error then run minikube delete and again start minikube.

[dhairya-seth]

/kind support

[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

[OksiBlack]

logs.txt

same error with podman

Creating podman container (CPUs=2, Memory=3855MB) ...
🤦  StartHost failed, but will try again: creating host: create: creating: setting up container node: preparing volume for podman-k8s-cluster container: podman run --rm --name podman-k8s-cluster-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=podman-k8s-cluster --entrypoint /usr/bin/test -v podman-k8s-cluster:/var gcr.io/k8s-minikube/kicbase:v0.0.47 -d /var/lib: exit status 126
stdout:

stderr:
Trying to pull gcr.io/k8s-minikube/kicbase:v0.0.47...
Getting image source signatures
Copying blob sha256:f4e12836666da9957009e2db170c8d9731690be5d46cc95882506a80312972f6
Copying config sha256:795ea6a69ce682944ae3f1bc8b732217eb065d3b981db69c80fd26ffbf05eda9
Writing manifest to image destination
Error: preparing container 80b2ddedd703b03a1e90fbcb22fca42a7480f0109202174326b8fad0ccbe4ee0 for attach: mounting storage for container 80b2ddedd703b03a1e90fbcb22fca42a7480f0109202174326b8fad0ccbe4ee0: creating overlay mount to /var/lib/containers/storage/overlay/addd967077d5c7cbac2771ecd240ec9d36ee5d7d7757e20807a9e036463e04d3/merged, mount_data="lowerdir=/var/lib/containers/storage/overlay/l/T2XMX4LBMOEL6AMCHXQZFVDD43,upperdir=/var/lib/containers/storage/overlay/addd967077d5c7cbac2771ecd240ec9d36ee5d7d7757e20807a9e036463e04d3/diff,workdir=/var/lib/containers/storage/overlay/addd967077d5c7cbac2771ecd240ec9d36ee5d7d7757e20807a9e036463e04d3/work,nodev,metacopy=on,volatile,context=\"system_u:object_r:container_file_t:s0:c641,c797\"": input/output error

🔄  Restarting existing podman container for "podman-k8s-cluster" ...
😿  Failed to start podman container. Running "minikube delete -p podman-k8s-cluster" may fix it: driver start: start: podman start podman-k8s-cluster: exit status 125
stdout:

stderr:
Error: no container with name or ID "podman-k8s-cluster" found: no such container

[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-sigs/prow repository.