-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
k3s doesn't work on Chrome OS Crostini #1116
Comments
Really want this to work on my Pixelbook please. |
It seems like the vxlan moduke is missing in the Crostini kernel |
Another pixelbook user here that needs this. |
Doen't work on my chromebook as well k3s service starts but i get no node would be great if someone can add chromebook support when possible Thanks |
I am seeing the same issue. The logs show that we are lack of OVERLAY_FS and BRIDGE_NETFILTER support. Similar issue for minikube here: kubernetes/minikube#6411 |
Based on https://twitter.com/ibuildthecloud/status/1571718481133064193 & https://twitter.com/ibuildthecloud/status/1571736993725566976 I just tried as:
And it seems to work just fine:
|
It doesn't fully work because iptables bridge filtering is not supported by the kernel. This will manifest itself easily by the fact that DNS is broken inside pods. Inside a pod just run "ping www.google.com" and you'll see the DNS fails to resolve. This is because the request going to 10.43.0.10 (for coredns) is not getting processed by the kube proxy iptables rules. |
Possibly there is an approach to use nftables instead of iptables. I haven't investigated that. |
Not planning on adding ChromeOS support at this time. |
Describe the bug
k3s fails on Crostini
To Reproduce
Install k3s and attempt to start Kubernetes cluster
Expected behavior
Kubernetes cluster starts
Actual behavior
Cluster fails to start
Additional context
Speaking with Darren Sheperd at Kubecon, he said that k3s would need some changes to work in Crostini, if it was even possible. I'm opening this issue as a reminder to please look into it.
The text was updated successfully, but these errors were encountered: