Port <xxxx> for service <abc> is already opened by another service
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, kubernetes, ocaml
- Domain
- devops, networking
Research direction
Start by reproducing the NodePort case on Docker Desktop for Windows 10 and inspect the vpnkit-controller pod logs for the repeated port-conflict error. Then investigate the outbound-request timeout and apparent TCP socket exhaustion using the Windows resource monitor. Done means determining whether the symptoms share a cause and documenting a reproducible diagnosis.
Written by the indexing model from the issue text.
Description
Getting this error every 30 seconds the moment I inject a service in my kubernetes cluster.
Using Docker Desktop on Windows 10, so vpnkit-controller is installed by the docker-desktop setup.
I've already reset the cluster several times and tried to reproduce this step by step.
Applying deployments to my cluster is no problem at all but the moment I apply a service to expose my pods to the cluster via NodePort I'm seeing these errors in the log of the vpnkit-controller pod. Port-forwarding still works and my services are available on my host machine but I'd like to understand what is going wrong here.
Plus I'm having an issue with outbound ports. When a pod issues a lot of external requests it randomly gets timeouts, apparently because tcp sockets are exhausted at some point. When looking in the resource monitor of windows I can see that vpnkit opens a lot of ports but it seems to keep them open. I'm not sure if both issues are connected but something is going on here and I'm not sure how to analyse it any further.
If you have an idea what could cause this - let me know. If you want to dig deeper and reproduce this, also let me know - I could provide a detailed example then.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from moby/vpnkit
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Compilation error due to "Unbound module Ethernet__Ethernet_wire"May be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
[Bug] web.deploymentStrategy and admintools.deploymentStrategy are ignored, and component ServiceAccounts have no namespacePossibly taken @wankhede04 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
temporalio/helm-charts#1006 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
opdev/vuln-scan-cert#44 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
s4u/setup-maven-action#172 ·
-
Add dependabotOpenfeat
Difficulty 2/5 Under an hour Newbie friendliness 72/100
open-nudge/opentemplate#204 ·
Maintainers usually reply within 1 day