Kubunetes still in a 'starting' state after half an hour.

[cbladd]

Description

Kubernetes won't start in docker desktop.

Reproduce

Start docker desktop. Wait for kubernetes to start. Keep waiting.

Expected behavior

Kubernetes enters a 'started' or 'ready' state.

docker version

docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:34 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:29:19 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

docker info

docker info
Client:
 Debug Mode: false

Server:
 Containers: 37
  Running: 4
  Paused: 0
  Stopped: 33
 Images: 115
 Server Version: 19.03.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.76-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 1.943GiB
 Name: docker-desktop
 ID: 7MVY:4KU3:XJYU:4RLW:UELW:CD54:YP4S:BXSR:FOKD:UTBE:K7LW:AZ6S
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 56
  Goroutines: 69
  System Time: 2023-10-15T00:05:04.752244443Z
  EventsListeners: 3
 HTTP Proxy: gateway.docker.internal:3128
 HTTPS Proxy: gateway.docker.internal:3129
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

Diagnostics ID

B82A2E26-21A9-4427-B040-3EC74A81C27A/20231015000012

Additional Info

No response

[sshahar1]

I am also experiencing this since upgrade to sonoma.

[danielskowronski]

I was experiencing the same issue on 4.25.0 (126437) when using macOS 14.2 Beta (23C5030f) - Docker Desktop was installed long time ago.

However, the issue is gone after a complete purge of Docker Desktop and fresh installation. Built-in options like Reset to factory defaults or Uninstall Docker Desktop didn't help - I had to use AppCleaner to get rid of everything. Reboot was not needed.

For reference, here's the list of files identified by AppCleaner:

/Applications/Docker.app
/Library/LaunchDaemons/com.docker.vmnetd.plist
/Library/PrivilegedHelperTools/com.docker.vmnetd
~/Library/Application Support/Docker Desktop
~/Library/Caches/Docker Desktop
~/Library/Containers/Docker
~/Library/Group Containers/group.com.docker

Unfortunately, I didn't dump diagnostic info before purging the app. IIRC, attempt to activate Kubernetes when it wasn't working wasn't even pulling necessary Docker images (as seen in Images tab in UI).

[zaafar]

In case someone doesn't want to use app-cleaner #7056 (comment) worked for me.

[jakepearson]

I tried both fix steps from @danielskowronski and @zaafar, but neither worked for me.

I'm experiencing something similar issue. I upgraded to osx Sonoma today. Once installed, I was no longer able to start my kubernetes cluster in docker desktop. When K8S is starting the apiserver gets into a crash loop with the following error:

2023-11-07 11:18:40 W1107 18:18:40.912772       1 logging.go:59] [core] [Channel #3 SubChannel #5] grpc: addrConn.createTransport failed to connect to {
2023-11-07 11:18:40   "Addr": "127.0.0.1:2379",
2023-11-07 11:18:40   "ServerName": "127.0.0.1",
2023-11-07 11:18:40   "Attributes": null,
2023-11-07 11:18:40   "BalancerAttributes": null,
2023-11-07 11:18:40   "Type": 0,
2023-11-07 11:18:40   "Metadata": null
2023-11-07 11:18:40 }. Err: connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:2379: connect: connection refused"

Maybe something in Sonoma has different networking configs?

[milas]

Docker Desktop 4.29 includes a bunch of fixes for the reliability of provisioning the built-in Kubernetes cluster.

Specifically for this issue:

• Startup will not hang indefinitely, it should succeed or fail
• It's now possible to disable Kubernetes while it's starting

Please upgrade (use "Check for updates" in Settings if it's not appearing, it was released recently so is still rolling out for automatic updates).

If you have problems after upgrading, try the "Reset Cluster" to re-create it.
(This will purge all your Kubernetes workloads!)