Error in configuration of minikube and podman

[rajendra0508]

What Happened?

I have installed minikube , kubectl and podman and now trying to configure these , i am using below command on windows and getting error:

 **minikube start --driver=podman --container-runtime=containerd**

Using the podman (experimental) driver based on user configuration

• Using rootless Podman driver
• Starting control plane node minikube in cluster minikube
• Pulling base image ...
  E1013 Error downloading kic artifacts: not yet implemented, see issue podman: load kic base image from cache if available for offline mode #8426
• Creating podman container (CPUs=2, Memory=4000MB) ...
  ! StartHost failed, but will try again: creating host: create: creating: setting up container node: preparing volume for minikube container: podman run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.40 -d /var/lib: exit status 125
  stdout:

stderr:
Trying to pull gcr.io/k8s-minikube/kicbase:v0.0.40...
Error: initializing source docker://gcr.io/k8s-minikube/kicbase:v0.0.40: pinging container registry gcr.io: Get "https://gcr.io/v2/": dial tcp: lookup gcr.io: Temporary failure in name resolution

• Restarting existing podman container for "minikube" ...
• 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

Attach the log file

na

Operating System

Windows

Driver

Podman

[chef-wally]

Same issue but on CentOS Stream 9.

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