kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.41k stars 4.88k forks source link

minikube installation error on ubuntu 22.04 LTS installed on widow 11 home 64 #18875

Closed whispercan9 closed 2 weeks ago

whispercan9 commented 5 months ago

What Happened?

I have successfully installed docker container in ubuntu and hello-world image runs fine.

Installation of minikube is also complete without any error but when I try to run

Docker Version: Client: Version: 24.0.5 API version: 1.43 Go version: go1.20.3 Git commit: 24.0.5-0ubuntu1~22.04.1 Built: Mon Aug 21 19:50:14 2023 OS/Arch: linux/amd64 Context: default

Server: Engine: Version: 24.0.5 API version: 1.43 (minimum version 1.12) Go version: go1.20.3 Git commit: 24.0.5-0ubuntu1~22.04.1 Built: Mon Aug 21 19:50:14 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.2 GitCommit: runc: Version: 1.1.7-0ubuntu1~22.04.2 GitCommit: docker-init: Version: 0.19.0

minikube version: v1.33.0

Config.json file details are:

{ "Name": "minikube", "KeepContext": false, "EmbedCerts": false, "MinikubeISO": "", "KicBaseImage": "gcr.io/k8s-minikube/kicbase:v0.0.43@sha256:7ff490df401cc0fbf19a4521544ae8f4a00cc163e92a95017a8d8bfdb1422737", "Memory": 3900, "CPUs": 2, "DiskSize": 20000, "Driver": "docker", "HyperkitVpnKitSock": "", "HyperkitVSockPorts": [], "DockerEnv": null, "ContainerVolumeMounts": null, "InsecureRegistry": null, "RegistryMirror": [], "HostOnlyCIDR": "192.168.59.1/24", "HypervVirtualSwitch": "", "HypervUseExternalSwitch": false, "HypervExternalAdapter": "", "KVMNetwork": "default", "KVMQemuURI": "qemu:///system", "KVMGPU": false, "KVMHidden": false, "KVMNUMACount": 1, "APIServerPort": 8443, "DockerOpt": null, "DisableDriverMounts": false, "NFSShare": [], "NFSSharesRoot": "/nfsshares", "UUID": "", "NoVTXCheck": false, "DNSProxy": false, "HostDNSResolver": true, "HostOnlyNicType": "virtio", "NatNicType": "virtio", "SSHIPAddress": "", "SSHUser": "root", "SSHKey": "", "SSHPort": 22, "KubernetesConfig": { "KubernetesVersion": "v1.30.0", "ClusterName": "minikube", "Namespace": "default", "APIServerHAVIP": "", "APIServerName": "minikubeCA", "APIServerNames": null, "APIServerIPs": null, "DNSDomain": "cluster.local", "ContainerRuntime": "docker", "CRISocket": "", "NetworkPlugin": "cni", "FeatureGates": "", "ServiceCIDR": "10.96.0.0/12", "ImageRepository": "", "LoadBalancerStartIP": "", "LoadBalancerEndIP": "", "CustomIngressCert": "", "RegistryAliases": "", "ExtraOptions": null, "ShouldLoadCachedImages": true, "EnableDefaultCNI": false, "CNI": "" }, "Nodes": [ { "Name": "", "IP": "192.168.49.2", "Port": 8443, "KubernetesVersion": "v1.30.0", "ContainerRuntime": "docker", "ControlPlane": true, "Worker": true } ], "Addons": { "default-storageclass": true, "storage-provisioner": true }, "CustomAddonImages": null, "CustomAddonRegistries": null, "VerifyComponents": { "apiserver": true, "system_pods": true }, "StartHostTimeout": 360000000000, "ScheduledStop": null, "ExposedPorts": [], "ListenAddress": "", "Network": "", "Subnet": "", "MultiNodeRequested": false, "ExtraDisks": 0, "CertExpiration": 94608000000000000, "Mount": false, "MountString": "/home/kauls:/minikube-host", "Mount9PVersion": "9p2000.L", "MountGID": "docker", "MountIP": "", "MountMSize": 262144, "MountOptions": [], "MountPort": 0, "MountType": "9p", "MountUID": "docker", "BinaryMirror": "", "DisableOptimizations": false, "DisableMetrics": false, "CustomQemuFirmwarePath": "", "SocketVMnetClientPath": "", "SocketVMnetPath": "", "StaticIP": "", "SSHAuthSock": "", "SSHAgentPID": 0, "GPUs": "", "AutoPauseInterval": 60000000000 }

All IP addresses on Ubuntu are:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:15:5d:3c:e8:49 brd ff:ff:ff:ff:ff:ff inet 172.17.183.150/20 brd 172.17.191.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::215:5dff:fe3c:e849/64 scope link valid_lft forever preferred_lft forever 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:11:3a:84:2c brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global docker0 valid_lft forever preferred_lft forever inet6 fe80::42:11ff:fe3a:842c/64 scope link valid_lft forever preferred_lft forever 4: br-dc411060c68a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:e2:ae:2b:2f brd ff:ff:ff:ff:ff:ff inet 192.168.49.1/24 brd 192.168.49.255 scope global br-dc411060c68a valid_lft forever preferred_lft forever inet6 fe80::42:e2ff:feae:2b2f/64 scope link valid_lft forever preferred_lft forever 8: vethf8bbd0c@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-dc411060c68a state UP group default link/ether 62:14:4a:16:4c:04 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::6014:4aff:fe16:4c04/64 scope link valid_lft forever preferred_lft forever

And I am also enclosing the minikube log file with it.

I have tried multiple things, but still no success, Any insights or directions on how to resolve it will be much appreciated.

Thanks

Attach the log file

minikube.txt

Operating System

Ubuntu

Driver

Docker

k8s-triage-robot commented 2 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 weeks ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 2 weeks ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/minikube/issues/18875#issuecomment-2405756236): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.