Restarting Docker Desktop resets Kind Kubernetes for v4.44

[practicusai]

Description

Starting with v4.44.* restarting docker desktop (intel) creates a new kubernetes cluster (kind) and everything in the k8s cluster is lost.

Reproduce

1. Start Docker desktop
2. Create a kind kubernetes cluster
3. create a namespace kubectl create namespace test
4. Quit Docker Desktop
5. Start Docker Desktop
6. Check namespaces kubectl get namespaces, verify test namespace is missing.

Expected behavior

Restarting Docker desktop does not reset kubernetes cluster

[ferranconde]

Same experience here. I just upgraded from 4.42.x to 4.44.x and my cluster got reset.

[hakan-77]

Any improvement on this? Happy to provide logs.

[java-plus-plus]

Same issue in MacOS, I have Docker Desktop Version 4.46.0 (204649).

This is a critical bug, the whole Kubernetes cluster is getting nuked every time I quick & reopen Docker Desktop or restart laptop itself.

4.44 -> 4.46 is quite a long version change, and this issue was created a month ago, still no updates on this bug?

[hakan-77]

Hi @bsousaa, this bug is basically rendering any version >= 4.44+ useless for Kubernetes on MacOS. Who would be the correct person to involve?

[java-plus-plus]

Hi @hakan-77 , I just confirmed that this bug is happening in Windows too.
My colleague with her Windows 10 office laptop is also facing the same issue.

[hakan-77]

I blame this on AI craze. Great, now we have MCP support in docker desktop (that I'm sure is very useful for some people) and suddenly everything else became secondary priority.

Local Kubernetes is the only reason we use docker desktop, and right now we are seriously considering a pure-Kind based solution.

[java-plus-plus]

I blame this on AI craze. Great, now we have MCP support in docker desktop (that I'm sure is very useful for some people) and suddenly everything else became secondary priority.

Local Kubernetes is the only reason we use docker desktop, and right now we are seriously considering a pure-Kind based solution.

Agreed.
After taking quick look at the release notes, looks like recent releases are mostly only primarily focused on AI stuff, and Docker Desktop's Docker and Kubernetes focus seems to kinda off lately.

[niyaz707ilm]

Same behaviour with KinD docker-desktop in windows as well. Where it resets the whole cluster even when docker-desktop is restarted with no update.

Alternate: Kubeadm

Even after docker restart the cluster and its resources persists.

[java-plus-plus]

Same behaviour with KinD docker-desktop in windows as well. Where it resets the whole cluster even when docker-desktop is restarted with no update.

Alternate: Kubeadm

Even after docker restart the cluster and its resources persists.

Confirmed the same, issue is occuring only with k8s with KIND, but isn't that what everyone's looking for now?

[bsousaa]

This issue has been fixed with Docker Desktop 4.48. Can you give it a try?

I'm closing the issue for the moment, but will re-open if needed.