Docker issue

[Isha-Yasin]

What Happened?

Docker is not running while its status is Running
And Minikube is also in issue
Error :
minikube start --image-repository=k8s.gcr.io
😄 minikube v1.33.1 on Ubuntu 22.04
✨ Using the qemu2 driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🏃 Updating the running qemu2 "minikube" VM ...
🌐 Found network options:
▪ HTTP_PROXY=http://proxy.example.com:8080
▪ NO_PROXY=localhost,127.0.0.1
❗ This VM is having trouble accessing https://registry.k8s.io
💡 To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
❗ Due to DNS issues your cluster may have problems starting and you may not be able to pull images
More details available at: https://minikube.sigs.k8s.io/docs/drivers/qemu/#known-issues
🐳 Preparing Kubernetes v1.30.0 on Docker 26.0.2 ...
▪ env HTTP_PROXY=http://proxy.example.com:8080
▪ env NO_PROXY=localhost,127.0.0.1
🤦 Unable to restart control-plane node(s), will reset cluster:
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
❗ Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://localhost:45449/apis/storage.k8s.io/v1/storageclasses": dial tcp 127.0.0.1:45449: connect: connection refused]
🌟 Enabled addons: storage-provisioner

❌ Exiting due to GUEST_START: failed to start node: wait 6m0s for node: wait for healthy API server: apiserver healthz never reported healthy: context deadline exceeded

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 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

~$ kubectl get node
E0802 17:10:09.996891 16912 memcache.go:265] couldn't get current server API group list: Get "https://localhost:45449/api?timeout=32s": dial tcp 127.0.0.1:45449: connect: connection refused
E0802 17:10:09.997139 16912 memcache.go:265] couldn't get current server API group list: Get "https://localhost:45449/api?timeout=32s": dial tcp 127.0.0.1:45449: connect: connection refused
E0802 17:10:09.998503 16912 memcache.go:265] couldn't get current server API group list: Get "https://localhost:45449/api?timeout=32s": dial tcp 127.0.0.1:45449: connect: connection refused
E0802 17:10:09.998714 16912 memcache.go:265] couldn't get current server API group list: Get "https://localhost:45449/api?timeout=32s": dial tcp 127.0.0.1:45449: connect: connection refused
E0802 17:10:10.000165 16912 memcache.go:265] couldn't get current server API group list: Get "https://localhost:45449/api?timeout=32s": dial tcp 127.0.0.1:45449: connect: connection refused
The connection to the server localhost:45449 was refused - did you specify the right host or port?

Operating System

Ubuntu

Driver

Docker

[Isha-Yasin]

kindly help quickly

[kundan2707]

/kind support

[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