Issues with wsl2
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 722
- Forks
- 48
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 8
Description
I am having networking issues still with wsl2. When I run the kind example for an internal registry it works fine. When I use ctptl it is not setting the the port to the random number, but is setting the registry port in the docket container to 500x
Contributor 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.
Research direction
Start by reproducing the kind internal-registry example and the equivalent ctlptl workflow on WSL2. Compare the random port assigned by ctlptl with the registry port exposed in the Docker container; done means the container uses the expected random port consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100