minikube was unable to download gcr.io/k8s-minikube/kicbase:v0.0.34

[Parthiba-Hazra]

What Happened?

After execute the command minikube start --driver=docker
First it continually pulling the gcr.io/k8s-minikube/kicbase and index.docker.io/kicbase/sta. even after 100% download . Then it shows minikube was unable to download gcr.io/k8s-minikube/kicbase:v0.0.34,

next I tried minikube delete and minikube start again
but it gives same error every time .

Os - Ubuntu 22.04

Attach the log file

Operating System

Ubuntu

Driver

Docker

[afbjorklund]

You can try with docker pull to see if it gives you a better error message ?

[Parthiba-Hazra]

You can try with docker pull to see if it gives you a better error message ?

Yes it's work, thank you @afbjorklund I pull the image gcr.io/k8s-minikube/kicbase and the error solved.

But the second error (Enabling 'default-storageclass' returned an error: running callbacks) yet not solved . can you help on that also?

[afbjorklund]

Sounds normal if the cluster is down

[Parthiba-Hazra]

hey @afbjorklund thank you for your support but I still cant find the solution as I am a new learner .
here in the logs of minikube ... it shows "Failed to find module 'autofs4'" and I am using ubuntu 22.04 LTS , I cant find what is broken :(

[afbjorklund]

Docker Desktop is not yet supported on Linux

Please provide the requested logs, next time

[Parthiba-Hazra]

here is the log file-
logs.txt

[afbjorklund]

I think the autofs4 (renamed to autofs) ssue can be added to the main issue about adding support for Docker Desktop on Linux

• minikube on driver docker not running using docker desktop vm #14202

It could be a false positive, or it could be an issue with the kernel version in the LinuxKit OS. Either way, it is not supported yet.

[Parthiba-Hazra]

Ok then I am going with Kvm ;)

[hemanthkotaprolu]

I am using docker desktop in linux(Pop OS). And it worked.
I did docker pull for the first error and it seemed to work and i am able to run the cluster.

[Parthiba-Hazra]

I am using docker desktop in linux(Pop OS). And it worked. I did docker pull for the first error and it seemed to work and i am able to run the cluster.

But sadly, it's not working in ubuntu-22.04.

[umiro]

But sadly, it's not working in ubuntu-22.04.

you may pull the lastest (10/17/2022, v0.0.35) container manually, and execute minikube start again.

docker pull gcr.io/k8s-minikube/kicbase@sha256:e6f9b2700841634f3b94907f9cfa6785ca4409ef8e428a0322c1781e809d311b

from https://gcr.io/k8s-minikube/kicbase -> https://console.cloud.google.com/gcr/images/k8s-minikube/GLOBAL/kicbase ->

[zioproto]

I had the same issue not being able to: minikube start on Mac with Docker Desktop.
The gcr.io/k8s-minikube/kicbase was stuck in download forever:

% minikube start
😄  minikube v1.27.1 on Darwin 12.6 (arm64)
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
    > gcr.io/k8s-minikube/kicbase:  0 B [__________________________] ?% ? p/s ?^C

Downloading the specific version as suggested fixed the problem:

docker pull gcr.io/k8s-minikube/kicbase@sha256:e6f9b2700841634f3b94907f9cfa6785ca4409ef8e428a0322c1781e809d311b

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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.

[mpostoronca]

Turn off your firewall and make sure DOCKER_DEFAULT_PLATFORM='' that's what helped me (on a macOS)