-
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
v1.3.1: sudo minikube start requires sudo with vm-driver none #5110
Comments
The none driver currently does require sudo. We are trying to get rid of this requirement in the next versions of minikube |
Yes that is correct, however when running |
Is your root user called "root" ? There was some error when UID 0 have weird names: #4995 if d == constants.DriverNone && u.Name != "root" {
exit.UsageT(`Please run with sudo. the vm-driver "{{.driver_name}}" requires sudo.`, out.V{"driver_name": constants.DriverNone}) On some systems, the superuser doesn't have a real name (only login name). Or a different one. |
Yes, the root user on my system is named "root". I also ran a simple golang script using the "os/user" import to confirm |
Just thought I would ask, because on Manjaro (I think it was) the root user was called "" package main
import (
"fmt"
"os/user"
)
func main() {
u, _ := user.Current()
fmt.Printf("User Name: %v\n", u.Name)
} $ sudo go run rootuser.go
[sudo] lösenord för anders:
User Name: root Anyway, the plan for "soon" is to have the none user run without root (i.e. call sudo for you) |
Thank you for following up with this clarifying context, it finally made me realise that there is a difference between I have set the display name for my root user via this command:
And now minikube starts up without complaint 🙂 Thank you for your help on this one! |
BTW: It is perfectly OK for root (or any user) to not have a display name, this is a bug in minikube. It even said so in the go docs: // Username is the login name.
Username string
// Name is the user's real or display name.
// It might be blank.
// On POSIX systems, this is the first (or only) entry in the GECOS field
// list.
// On Windows, this is the user's display name.
// On Plan 9, this is the contents of /dev/user.
Name string "It might be blank." (i.e. Probably wasn't the best of moves (from go) to rename the |
Is it a bug? Or an undocumented feature? Using display name could be intended as a way to work around scenarios where the administrative username is not "root" 🤔 |
Basically nobody cares about the GECOS. Anyway we should be checking user id, not user name. i.e. The superuser doesn't actually have to be called But I can't really recall anyone but |
@afbjorklund may be I can send a pr to fix it? Aaa, we already have #4745 |
Hi, "sudo minikube start --vm-driver=none" while executing this command I am getting the error as sorry,minikube is crashed I am facing this issue, can anyone give me the suggestion to overcome this problem. |
The exact command to reproduce the issue:
sudo minikube start
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version: 5.2.8-arch1-1-ARCH
The text was updated successfully, but these errors were encountered: