You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you expected to happen:
On ubuntu, service unit files are under /lib/systemd/system.
The right place to create systemd unit files should be /etc/systems/system which is unified across all systemd based distributions.
How to reproduce it (as minimally and precisely as possible):
minikube start --vm-driver=none
The constant LocalkubeServicePath should be /etc/systemd/system which is consistent across different distributions.
In none.go, the constants should be used instead of a string literal. Actually, mkdir is not necessary here.
The text was updated successfully, but these errors were encountered:
easeway
pushed a commit
to easeway/minikube
that referenced
this issue
Oct 20, 2017
Uh oh!
There was an error while loading. Please reload this page.
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
Minikube version : v0.22.3 (commit id: 3358402)
What happened:
E1020 10:45:30.305707 13466 start.go:150] Error starting host: Error starting stopped host: mkdir /usr/lib/systemd/system/: permission denied.
What you expected to happen:
On ubuntu, service unit files are under /lib/systemd/system.
The right place to create systemd unit files should be /etc/systems/system which is unified across all systemd based distributions.
How to reproduce it (as minimally and precisely as possible):
minikube start --vm-driver=none
Output of
minikube logs
(if applicable):Anything else do we need to know:
The constant
LocalkubeServicePath
should be/etc/systemd/system
which is consistent across different distributions.In
none.go
, the constants should be used instead of a string literal. Actually,mkdir
is not necessary here.The text was updated successfully, but these errors were encountered: