kong don't start

[median-dxz]

What happened?

Firstly, I know that it's a duplicate of #8765 and #8846.
But I'm using Kubernetes on Docker Desktop for Windows and I faced exactly the same problem. And I have tried clearing the previous minikube installnation thoroughly but still have the bind 8444 error.
It might not be minikube causing the problem？

What did you expect to happen?

Kong started normally

How can we reproduce it (as minimally and precisely as possible)?

exec helm command from readme

Anything else we need to know?

No response

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.3.1

Kubernetes version

Client Version: v1.29.1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.1

Dev environment

No response

[floreks]

I can't tell you what is occupying this port for you. Only you can debug your system and figure it out. You either free up this port or override the port that kong is using by default via helm chart values.

There is nothing we can do here since this is a configuration issue on your side.

[median-dxz]

I can't tell you what is occupying this port for you. Only you can debug your system and figure it out. You either free up this port or override the port that kong is using by default via helm chart values.

There is nothing we can do here since this is a configuration issue on your side.

Thanks you patiently reply.
I'm still learning about k8s, if you can provide some info so that I can troubleshoot the truely problem, I'll be very appreciately. I just have no idea how check out "port occupying" in a cluster.
Of course, there might not a suitable place for such a discuss, you can close this issue if needed.

UPD: After an afternoon of attempts, I completely reinstalled Docker Desktop, and after redeploying all the components I needed, I used kubectl debug to debug the pod with an ephemeral debug container (still need to change helm chart values). I found that I could bind port 8444 using nc within the temporary container.😭

[AndeYashwanth]

I faced this issue in docker desktop windows 4.28.0 yesterday when using the helm method. The port it was complaining wasn't being used by any process. So I installed the older 2.7.x version using the yaml file instead and it was working fine.
I tried clean installing docker desktop and also updated to 4.29.0 in an attempt to fix some other unrelated issue. Then I tried installing latest kubernetes dashboard 7.x and it was working fine.

[median-dxz]

Hi, @AndeYashwanth

That works for me too! Docker Desktop just recently released version 4.29.0. (it's a bit strange that the official Docker release notes page shows this version was released on 04-08, but I couldn't receive it when I opened this issue.). And after updating from 4.28.0 to 4.29.0, I was able to start Kong with Helm using the default values (no need to reinstall Docker Desktop entirely). This proves that it‘s Docker Desktop causing this issue.

Thank you for your help!