Skip to content

Unable to load cached images: loading cached images: stat /root/.minikube/cache/images/amd64/registry.k8s.io/coredns/coredns_v1.9.3: no such file or directory #20920

Open
@MHRScdr

Description

@MHRScdr

What Happened?

root@hosseinime-pc:/usr/local/bin# minikube start --driver=docker --force
๐Ÿ˜„ minikube v1.30.0 on Ubuntu 20.04 (amd64)
โ— minikube skips various validations when --force is supplied; this may lead to unexpected behavior
โœจ Using the docker driver based on existing profile
๐Ÿ›‘ The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force.
๐Ÿ’ก If you are running minikube within a VM, consider using --driver=none:
๐Ÿ“˜ https://minikube.sigs.k8s.io/docs/reference/drivers/none/
๐Ÿ’ก Tip: To remove this root owned cluster, run: sudo minikube delete
โ— docker is currently using the overlayfs storage driver, consider switching to overlay2 for better performance
๐Ÿ‘ Starting control plane node minikube in cluster minikube
๐Ÿšœ Pulling base image ...
โ— The image 'registry.k8s.io/kube-scheduler:v1.26.3' was not found; unable to add it to cache.
โ— The image 'registry.k8s.io/etcd:3.5.6-0' was not found; unable to add it to cache.
โ— The image 'registry.k8s.io/kube-controller-manager:v1.26.3' was not found; unable to add it to cache.
โ— The image 'registry.k8s.io/kube-apiserver:v1.26.3' was not found; unable to add it to cache.
โ— The image 'registry.k8s.io/coredns/coredns:v1.9.3' was not found; unable to add it to cache.
โ— The image 'registry.k8s.io/kube-proxy:v1.26.3' was not found; unable to add it to cache.
โ— The image 'registry.k8s.io/pause:3.9' was not found; unable to add it to cache.
๐Ÿƒ Updating the running docker "minikube" container ...
โ— The image 'gcr.io/k8s-minikube/storage-provisioner:v5' was not found; unable to add it to cache.
โ— Image was not built for the current minikube version. To resolve this you can delete and recreate your minikube cluster using the latest images. Expected minikube version: v1.29.0 -> Actual minikube version: v1.30.0
๐Ÿณ Preparing Kubernetes v1.26.3 on Docker 23.0.2 ...
โŒ Unable to load cached images: loading cached images: stat /root/.minikube/cache/images/amd64/registry.k8s.io/coredns/coredns_v1.9.3: no such file or directory

โŒ Exiting due to K8S_INSTALL_FAILED: Failed to update cluster: updating control plane: downloading binaries: downloading kubeadm: download failed: https://dl.k8s.io/release/v1.26.3/bin/linux/amd64/kubeadm?checksum=file:https://dl.k8s.io/release/v1.26.3/bin/linux/amd64/kubeadm.sha256: getter: &{Ctx:context.Background Src:https://dl.k8s.io/release/v1.26.3/bin/linux/amd64/kubeadm?checksum=file:https://dl.k8s.io/release/v1.26.3/bin/linux/amd64/kubeadm.sha256 Dst:/root/.minikube/cache/linux/amd64/v1.26.3/kubeadm.download Pwd: Mode:2 Umask:---------- Detectors:[0x3deaf98 0x3deaf98 0x3deaf98 0x3deaf98 0x3deaf98 0x3deaf98 0x3deaf98] Decompressors:map[bz2:0xc000057e70 gz:0xc000057e78 tar:0xc000057e20 tar.bz2:0xc000057e30 tar.gz:0xc000057e40 tar.xz:0xc000057e50 tar.zst:0xc000057e60 tbz2:0xc000057e30 tgz:0xc000057e40 txz:0xc000057e50 tzst:0xc000057e60 xz:0xc000057e80 zip:0xc000057e90 zst:0xc000057e88] Getters:map[file:0xc0004b66b0 http:0xc000738d20 https:0xc000738d70] Dir:false ProgressListener:0x3da6e40 Insecure:false DisableSymlinks:false Options:[0x1c778e0]}: invalid checksum: Error downloading checksum file: bad response code: 403

โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ โ”‚
โ”‚ ๐Ÿ˜ฟ 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. โ”‚
โ”‚ โ”‚
โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ

root@hosseinime-pc:/usr/local/bin# minikube start
๐Ÿ˜„ minikube v1.30.0 on Ubuntu 20.04 (amd64)
โœจ Using the docker driver based on existing profile
๐Ÿ›‘ The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force.
๐Ÿ’ก If you are running minikube within a VM, consider using --driver=none:
๐Ÿ“˜ https://minikube.sigs.k8s.io/docs/reference/drivers/none/
๐Ÿ’ก Tip: To remove this root owned cluster, run: sudo minikube delete

โŒ Exiting due to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.

i want to running minikube on ubuntu on wsl.

Attach the log file

log.txt

log.txt

Operating System

Ubuntu

Driver

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions