Driver=none 'CHANGE_MINIKUBE_NONE_USER' regression in v1.3.0 #5014
Labels
co/none-driver
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Problem
Regression in recent minikube
v1.3.0
whenCHANGE_MINIKUBE_NONE_USER=true
stopped to work properly.It's expected to set
.minikube
dir ownership to the user running sudo whenvmdriver=none
(per CI testing example), howeverroot
is used.Most probably regression introduced in #4737 and so
chown
is not executed as a last step when cluster is started.The exact command to reproduce the issue:
Unexpected files ownership (root):
Comparing to minikube
1.2.0
with correct files ownership:The operating system version:
Ubuntu 16.04.5 LTS
The text was updated successfully, but these errors were encountered: