minikube: None driver error on minikube 1.11.0
Since first versions of minikube I had a bad experience with driver none, and a would really like to get it working without VMs. Even using KVM2 I think it wastes resources and have poor performance.
Steps to reproduce the issue:
- minikube start --vm-drive=none
Full output of failed command:
$ sudo minikube start --vm-driver=none --alsologtostderr
I0602 17:21:13.290278 51066 start.go:98] hostinfo: {"hostname":"static-Aspire-R5-471T","uptime":35216,"bootTime":1591094057,"procs":374,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"20.04","kernelVersion":"5.4.0-33-generic","virtualizationSystem":"kvm","virtualizationRole":"host","hostid":"65f6c450-e2bf-81e5-328e-441ca823e081"}
I0602 17:21:13.291406 51066 start.go:108] virtualization: kvm host
😄 minikube v1.11.0 on Ubuntu 20.04
I0602 17:21:13.295673 51066 driver.go:253] Setting default libvirt URI to qemu:///system
✨ Using the none driver based on user configuration
I0602 17:21:13.296039 51066 notify.go:125] Checking for updates...
I0602 17:21:13.298818 51066 start.go:214] selected driver: none
I0602 17:21:13.298839 51066 start.go:611] validating driver "none" against <nil>
I0602 17:21:13.298855 51066 start.go:617] status for none: {Installed:true Healthy:true Error:<nil> Fix: Doc:}
I0602 17:21:13.299021 51066 start_flags.go:218] no existing cluster config was found, will generate one from the flags
I0602 17:21:13.299201 51066 start_flags.go:232] Using suggested 2200MB memory alloc based on sys=7843MB, container=0MB
I0602 17:21:13.299376 51066 start_flags.go:556] Wait components to verify : map[apiserver:true system_pods:true]
👍 Starting control plane node minikube in cluster minikube
I0602 17:21:13.302962 51066 profile.go:156] Saving config to /root/.minikube/profiles/minikube/config.json ...
I0602 17:21:13.303093 51066 lock.go:35] WriteFile acquiring /root/.minikube/profiles/minikube/config.json: {Name:mk270d1b5db5965f2dc9e9e25770a63417031943 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0602 17:21:13.303310 51066 exit.go:58] WithError(error provisioning host)=Failed to save config: failed to acquire lock for /root/.minikube/profiles/minikube/config.json: {Name:mk270d1b5db5965f2dc9e9e25770a63417031943 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}: unable to open /tmp/juju-mk270d1b5db5965f2dc9e9e25770a63417031943: permission denied called from:
goroutine 1 [running]:
runtime/debug.Stack(0x40c11a, 0x187eca0, 0x1982e80)
/usr/local/go/src/runtime/debug/stack.go:24 +0x9d
k8s.io/minikube/pkg/minikube/exit.WithError(0x1ae579a, 0x17, 0x1db6b80, 0xc00010de20)
/app/pkg/minikube/exit/exit.go:58 +0x34
k8s.io/minikube/cmd/minikube/cmd.runStart(0x2b00360, 0xc000777220, 0x0, 0x2)
/app/cmd/minikube/cmd/start.go:169 +0xac2
github.com/spf13/cobra.(*Command).execute(0x2b00360, 0xc000777200, 0x2, 0x2, 0x2b00360, 0xc000777200)
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:846 +0x2aa
github.com/spf13/cobra.(*Command).ExecuteC(0x2b05220, 0x0, 0x1, 0xc00078ea40)
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950 +0x349
github.com/spf13/cobra.(*Command).Execute(...)
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
k8s.io/minikube/cmd/minikube/cmd.Execute()
/app/cmd/minikube/cmd/root.go:112 +0x747
main.main()
/app/cmd/minikube/main.go:66 +0xea
❌ [JUJU_LOCK_DENIED] error provisioning host Failed to save config: failed to acquire lock for /root/.minikube/profiles/minikube/config.json: {Name:mk270d1b5db5965f2dc9e9e25770a63417031943 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}: unable to open /tmp/juju-mk270d1b5db5965f2dc9e9e25770a63417031943: permission denied
💡 Suggestion: Run 'sudo sysctl fs.protected_regular=0', or try a driver which does not require root, such as '--driver=docker'
⁉️ Related issue: https://github.com/kubernetes/minikube/issues/6391
Full output of minikube start command used, if not already included:
N/A
Optional: Full output of minikube logs command:
$ minikube logs
🤷 There is no local cluster named "minikube"
👉 To fix this, run: "minikube start"
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (10 by maintainers)
https://github.com/juju/mutex/issues/7
But the last commit is from Jun 2018, whereas the systemd breakage is from Feb 2019