-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Minikube does not work on Travis arm64
with LXD
#11845
Comments
See #7957 for some earlier discussion, supporting LXC/LXD is not a top priority at the moment |
@afbjorklund while we dont support LXD drivers,,, but may be we could support none driver on lxd ? I wonder what are the missing pieces for none driver |
The none driver is unlikely to work with a fakenode, without some similar hacks as the KIC image. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
I've been struggling to get Minikube to work with Travis's
arm64
runners. These are run within LXD images on Packet.net (now Equinix) machines. I have no ability to change the configuration of these runners.The runners do have Docker installed.
Using the
docker
driver failsThe docker driver (GoogleContainerTools/container-debug-support@ff8acb3) fails (full log) due to #6411:
Using the
none
driver failsAfter a lot of trial and error (GoogleContainerTools/container-debug-support@ba6472d), my command line is:
TERM=dumb sudo -E $HOME/bin/minikube start --driver=none --alsologtostderr -v=5 --feature-gates="LocalStorageCapacityIsolation=false" --extra-config=kubelet.protect-kernel-defaults=true
. But:/proc/sys
.The
LocalStorageCapacityIsolation
is required as I was getting errors likekubelet.go:1367] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 60 in cached partitions map
and this check could be disabled.The
--extra-config=kubelet.protect-kernel-defaults=true
was an attempt to work around errors trying to set specific sysctl values via/proc/sys
. Now it fails as the retrieved values don't match what it wants to see.At this point, the kubelet fails like the following (full log):
The text was updated successfully, but these errors were encountered: