-
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
none: writing kubeconfig: unable to open /tmp/juju-x: permission denied (sysctl fs.protected_regular=0) #6391
Comments
Looks like this is a new feature in systemd version 241 (minikube uses version 240):
Basically root is not allowed to read the users files, which breaks github.com/juju/mutex To reproduce:
$ touch /tmp/foo
$ chmod 600 /tmp/foo
$ sudo tee /tmp/foo
tee: /tmp/foo: Åtkomst nekas
^C To disable:
|
The best long-term fix here would be to stop having to run minikube with sudo...
|
That's some catch, very good job! It does indeed seems to be the issue. I'm very much looking forward to the day when sudo won't be necessary. I the meantime I think I will resort to using the virtualbox driver. |
I stumbled upon this the cli helpfully brought mere here:
Interestingly the suggestion |
@FlorianLudwig : It was fixed in 644b419 |
Failed to start none bare metal machine. Running "minikube delete" may fix it: boot lock: unable to open /tmp/juju-mkc8ab01ad3ea83211c |
WHAT HAPPENED** root@ip-172-31-42-227:/home/ubuntu# sudo minikube start --force
X Exiting due to HOST_JUJU_LOCK_PERMISSION: Failed to start host: boot lock: unable to open /tmp/juju-mkc8ab01ad3ea83211c505c81a7ee49a8e3ecb89: permission denied
WHEN START MINIKUBE OPERATIING SYSTEM DRIVER |
Change the recursive Permissions to root on /tmp folder chown -R root:root /tmp It worked for me in kubernetes version 1.26 |
The exact command to reproduce the issue:
The full output of the command that failed:
(Sorry, my terminal isn't so fancy.)
The mentioned file has the following permissions and ownership.
For reference, «jonas» is the user I am invoking
sudo
as.Interestingly, I can log in as root (ie.
SUDO_UID
andSUDO_GID
won't be present) and run the same commands successfully.However, nothing seems to be actually stopped, all the containers are still running.
The output of the
minikube logs
command:The operating system version:
I use Arch Linux btw.
The text was updated successfully, but these errors were encountered: