Kong pod doesn't start

### What happened? ### Issue I've seen other issues related to this https://github.com/kubernetes/dashboard/issues/8909 https://github.com/kubernetes/dashboard/issues/8765. https://github.com/kubernetes/dashboard/issues/8909 is similar to my issue. I faced this issue previously which got fixed by upgrading docker from 4.28.0 to 4.29.0 and reinstalling dashboard. Now I had to reinstall docker for different reason and I'm facing the issue again. I see some comments mentioning 8444 port is being used by minikube. In my case 8444 port is free and I dont have minikube. But I have tomcat on 8443. ### Workaround Only workaround is to delete the kong pod which makes the pod start successfully. But after restarting windows the issue reappears. ### Environment OS: Windows Docker Desktop version: 4.38.0 (181591) I access dashboard with https://localhost:32443/ instead of port forward. Maybe I enabled nodeport. I don't remember. ``` >kubectl logs kubernetes-dashboard-kong-678c76c548-gkxdr -n kubernetes-dashboard Defaulted container "proxy" out of: proxy, clear-stale-pid (init) 2025/09/17 03:54:18 [warn] 1#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /kong_prefix/nginx.conf:7 nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /kong_prefix/nginx.conf:7 2025/09/17 03:54:18 [notice] 1#0: [lua] init.lua:791: init(): [request-debug] token for request debugging: 7e6103b3-2a41-47a8-a04e-baad72f87342 2025/09/17 03:54:18 [emerg] 1#0: bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) nginx: [emerg] bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) 2025/09/17 03:54:18 [notice] 1#0: try again to bind() after 500ms 2025/09/17 03:54:18 [emerg] 1#0: bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) nginx: [emerg] bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) 2025/09/17 03:54:18 [notice] 1#0: try again to bind() after 500ms 2025/09/17 03:54:18 [emerg] 1#0: bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) nginx: [emerg] bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) 2025/09/17 03:54:18 [notice] 1#0: try again to bind() after 500ms 2025/09/17 03:54:18 [emerg] 1#0: bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) nginx: [emerg] bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) 2025/09/17 03:54:18 [notice] 1#0: try again to bind() after 500ms 2025/09/17 03:54:18 [emerg] 1#0: bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) nginx: [emerg] bind() to unix:/kong_prefix/sockets/we failed (98: Address already in use) 2025/09/17 03:54:18 [notice] 1#0: try again to bind() after 500ms 2025/09/17 03:54:18 [emerg] 1#0: still could not bind() nginx: [emerg] still could not bind() ``` ### What did you expect to happen? Kubernetes dashboard should start and be accessible ### How can we reproduce it (as minimally and precisely as possible)? Issue is happening after installing kubernetes dashboard via helm. ### Anything else we need to know? _No response_ ### What browsers are you seeing the problem on? _No response_ ### Kubernetes Dashboard version 7.13.0 ### Kubernetes version Client Version: v1.31.4 Kustomize Version: v5.4.2 Server Version: v1.31.4 ### Dev environment _No response_