Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube cluster creation failure on Podman Desktop #18039

Open
xbabalov opened this issue Jan 25, 2024 · 7 comments
Open

Minikube cluster creation failure on Podman Desktop #18039

xbabalov opened this issue Jan 25, 2024 · 7 comments
Labels
co/podman-driver podman driver issues lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/windows

Comments

@xbabalov
Copy link

What Happened?

When trying to create a Minikube cluster in Resources in Podman Desktop, I get a following error even while having a rootful podman machine running.

Steps to reproduce:

  1. Install Podman Desktop
  2. Install and initialize Podman with rootful machine
  3. Install Minikube
  4. Try to create a Minikube cluster

Screenshot:
minikube error on rootful machine

Error:
Error: Failed to create minikube cluster. E0125 05:58:08.614734 408 cache.go:189] Error downloading kic artifacts: not yet implemented, see issue #8426 ! StartHost failed, but will try again: driver start: start: podman start minikube: exit status 125 stdout: stderr: Error: no container with name or ID "minikube" found: no such container * Failed to start podman container. Running "minikube delete" may fix it: driver start: start: podman start minikube: exit status 125 stdout: stderr: Error: no container with name or ID "minikube" found: no such container X Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: start: podman start minikube: exit status 125 stdout: stderr: Error: no container with name or ID "minikube" found: no such container * ╭─────────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ * If the above advice does not help, please let us know: │ │ https://github.com/kubernetes/minikube/issues/new/choose │ │ │ │ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯

Attach the log file

minikube_logs_12188603c5e9f28dcb94d82bb148706dd9bd0495_0.log

Operating System

Windows

Driver

Podman

@ismaelhamed
Copy link

Same here

@afbjorklund afbjorklund added co/podman-driver podman driver issues os/windows labels Apr 2, 2024
@wfschneider
Copy link

This was working for me last week but since I restarted my Mac I can no longer start minikube with podman.

@bobsira
Copy link

bobsira commented Jun 3, 2024

podman error

I am getting the following error when I run this on a windows machine: Error: Failed to create minikube cluster. * Exiting due to PROVIDER_PODMAN_NOT_FOUND: The 'podman' provider was not found: exec: "podman": executable file not found in %PATH% * Suggestion: Install Podman * Documentation: https://minikube.sigs.k8s.io/docs/drivers/podman/

However spinning up a cluster from the command line using this command: minikube start --driver=podman --container-runtime=cri-o is a successful.

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 1, 2024
@alexnelsone
Copy link

For anyone who may be coming here that is experiencing this issue on an M series Mac and podman. Running the following may clear up the issue with Error: no container with name or ID "minikube" found: no such container:

  1. minikube delete
  2. minikube config set rootless true
  3. minikube start --driver=podman --container-runtime=cri-o

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 26, 2024
@odockal
Copy link

odockal commented Nov 6, 2024

Still seeing the issue as of today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/podman-driver podman driver issues lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/windows
Projects
None yet
Development

No branches or pull requests

9 participants