Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with wsl2 #124

Open
chrislovecnm opened this issue Jun 14, 2021 · 1 comment
Open

Issues with wsl2 #124

chrislovecnm opened this issue Jun 14, 2021 · 1 comment

Comments

@chrislovecnm
Copy link

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

@nicks
Copy link
Member

nicks commented Jun 14, 2021

I'm not sure I understand the issue.

Are you saying that it's setting up the registry on a different port than you expect?

Or that it's setting the port correctly in Docker but not in the Kind cluster?

something else?

It might be easier to use a pre-determined port like in this example:
https://github.com/tilt-dev/ctlptl#kind-with-a-built-in-registry-at-a-pre-determined-port

rather than using a random port and then reading the random port back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants