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

Update kind instruction for Mac #148

Closed
wants to merge 1 commit into from
Closed

Update kind instruction for Mac #148

wants to merge 1 commit into from

Conversation

owenthereal
Copy link
Contributor

For Mac, kubectl logs accesses the Krustlet process running on the host.
The default gateway is the en0 interface IP on the host.

Discussion: https://bytecodealliance.zulipchat.com/#narrow/stream/227959-wasmtime-on.20k8s/topic/Krustlet/near/192599630
Ref 1: moby/moby#22753 (comment)
Ref 2: https://docs.docker.com/docker-for-mac/networking/#use-cases-and-workarounds

For Mac, `kubectl logs` accesses the Krustlet process running on the host.
The default gateway is the en0 interface IP on the host.

Discussion: https://bytecodealliance.zulipchat.com/#narrow/stream/227959-wasmtime-on.20k8s/topic/Krustlet/near/192599630
Ref 1: moby/moby#22753 (comment)
Ref 2: https://docs.docker.com/docker-for-mac/networking/#use-cases-and-workarounds
@bacongobbler
Copy link
Collaborator

bacongobbler commented Apr 1, 2020

Hey @jingweno! I grabbed my laptop and started looking into this issue further. I wrote up my findings over in #147, which looks to cover the documentation provided here with additional context.

I found the following:

  • I can confirm that the en0 network is reachable from within the container
  • Because a container can reach the en0 network, you should not need to provide a --node-ip, as Krustlet will start listening on the 192.168.1.* address by default
  • I attached some links that should help the next user caught up in this mess.

Would it be okay if we went ahead with #147 instead? I feel that PR provides a little more information for the user to dig into this issue further and hopefully equip them with more tools to dive into the deep end with this.

Thanks again!

@owenthereal
Copy link
Contributor Author

owenthereal commented Apr 1, 2020

@bacongobbler Yes, feel free to close this one.

Because a container can reach the en0 network, you should not need to provide a --node-ip, as Krustlet will start listening on the 192.168.1.* address by default

This doesn't seem to always work for me. As discussed in https://bytecodealliance.zulipchat.com/#narrow/stream/227959-wasmtime-on.20k8s/topic/Krustlet/near/192597480, on VPN, krustlet detected the interface okay; Off VPN, I got:

./krustlet-wasi --pfx-password password
thread 'main' panicked at 'unable to get default node IP address: failed to lookup address information: nodename nor servname provided, or not known', crates/kubelet/src/config.rs:92:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@bacongobbler
Copy link
Collaborator

Thanks for reminding me about that particular case. I'll make sure to call that out.

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

Successfully merging this pull request may close these issues.

None yet

2 participants