Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CHANGE_MINIKUBE_NONE_USER env variable not setting config.json ownership #3751

Closed
nhanda03 opened this issue Feb 25, 2019 · 1 comment
Closed

CHANGE_MINIKUBE_NONE_USER env variable not setting config.json ownership #3751

nhanda03 opened this issue Feb 25, 2019 · 1 comment
Labels
co/none-driver help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@nhanda03
Copy link

nhanda03 commented Feb 25, 2019 •
edited
Loading

Description
Even after setting the CHANGE_MINIKUBE_NONE_USER env variable the config.json is still owned by root.

export CHANGE_MINIKUBE_NONE_USER=true
sudo -E minikube start --vm-driver=none 
sudo ls -lrt  /home/ubuntu/.minikube/machines/minikube/config.json

Output
-rw------- 1 root root 2123 Feb 25 15:33 /home/ubuntu/.minikube/machines/minikube/config.json

minikube version: v0.34.1
OS: ubuntu 16.04 on EC2(AWS)
@tstromberg tstromberg changed the title CHANGE_MINIKUBE_NONE_USER env variable not working as expected CHANGE_MINIKUBE_NONE_USER env variable not setting config.json ownership Mar 8, 2019
@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. co/none-driver priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 8, 2019
@steved steved mentioned this issue Mar 14, 2019
Merged
@tstromberg
Copy link
Contributor

I believe this issue was resolved in the v1.1.0 release. Please try upgrading to the latest release of minikube, and if the same issue occurs, please re-open this bug. Thank you opening this bug report, and for your patience!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/none-driver help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tstromberg @nhanda03