Repository navigation
Restarting Docker Desktop resets Kind Kubernetes for v4.44 #7745
Description
Description
Starting with v4.44.* restarting docker desktop (intel) creates a new kubernetes cluster (kind) and everything in the k8s cluster is lost.
Reproduce
- Start Docker desktop
- Create a kind kubernetes cluster
- create a namespace
kubectl create namespace test - Quit Docker Desktop
- Start Docker Desktop
- Check namespaces
kubectl get namespaces, verifytestnamespace is missing.
Expected behavior
Restarting Docker desktop does not reset kubernetes cluster
Reacted by Shashwat Jain, Utku Birkan, Randy McCright, Jishnu Raj and Practicus AI
Activity
ferranconde commentedon Aug 25, 2025
Same experience here. I just upgraded from 4.42.x to 4.44.x and my cluster got reset.
hakan-77 commentedon Sep 11, 2025
Any improvement on this? Happy to provide logs.
java-plus-plus commentedon Sep 15, 2025
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 commentedon Sep 15, 2025
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 commentedon Sep 19, 2025
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 commentedon Sep 19, 2025
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 commentedon Sep 23, 2025
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 commentedon Sep 30, 2025
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 commentedon Oct 3, 2025
Confirmed the same, issue is occuring only with k8s with KIND, but isn't that what everyone's looking for now?
bsousaa commentedon Oct 10, 2025
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.
practicusai commentedon Oct 11, 2025
@bsousaa it now works. thanks.
small hiccup: new version requires to switch to the docker-desktop k8s context before starting DD, or else K8s start hangs.
Issue and recommend solution: #7771