Permission denied on non-existing /etc/rancher/k3s/config.yaml after fresh install

[soupdiver]

Environmental Info:
K3s Version:
k3s version v1.26.3+k3s1 (01ea3ff)
go version go1.19.7

Node(s) CPU architecture, OS, and Version:
Linux ubuntu 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
1 server

Describe the bug:
After a fresh installation using the quick start guide I get the error FATA[0000] open /etc/rancher/k3s/config.yaml: permission denied for any kubectl or k3s kubectl command I run without sudo.
The thing is, that file doesnt even exist:

sudo ls -la /etc/rancher/k3s
total 12
drw-r--r-- 2 felix root 4096 Apr 11 23:50 .
drwxr-xr-x 4 root  root 4096 Apr 11 23:24 ..
-rw------- 1 felix root 2961 Apr 12 09:34 k3s.yaml

Steps To Reproduce:

• Installed K3s:

Expected behavior:
I can run kubectl without sudo

Actual behavior:
I must use sudo for every kubectl command

Additional context / logs:

[osodracnai]

please start the server with --write-kubeconfig-mode to modify kube config permissions, you can find more about it here

[soupdiver]

I have added --write-kubeconfig-mode 644 to my systemd unit file, reloaded and restarted

sudo systemctl daemon-reload
sudo systemctl restart k3s
kubectl get pod
FATA[0000] open /etc/rancher/k3s/config.yaml: permission denied

[brandond]

The k3s command-line tools also need access to read the config file, or at least see if it exists. Your user doesn't have read access to the k3s directory, so it can't even see if it exists.

This is just basic Unix permissions stuff. You can continue to use sudo, or grant the owner and group search access to the directory: chmod ug+x /etc/rancher/k3s

[soupdiver]

ll /etc/rancher/k3s
ls: cannot access '/etc/rancher/k3s/..': Permission denied
ls: cannot access '/etc/rancher/k3s/.': Permission denied
ls: cannot access '/etc/rancher/k3s/k3s.yaml': Permission denied
total 0
d????????? ? ? ? ?            ? .
d????????? ? ? ? ?            ? ..
-????????? ? ? ? ?            ? k3s.yaml

felix@ubuntu  % sudo chmod ug+x /etc/rancher/k3s
felix@ubuntu  % ll /etc/rancher/k3s
ls: cannot access '/etc/rancher/k3s/..': Permission denied
ls: cannot access '/etc/rancher/k3s/.': Permission denied
ls: cannot access '/etc/rancher/k3s/k3s.yaml': Permission denied
total 0
d????????? ? ? ? ?            ? .
d????????? ? ? ? ?            ? ..
-????????? ? ? ? ?            ? k3s.yaml
felix@ubuntu  % kubectl get pod
FATA[0000] open /etc/rancher/k3s/config.yaml: permission denied

Does not seem to have the desired effect

[soupdiver]

I had to do a sudo chmod -R o+x /etc/rancher to fix the permissions. The change you suggested was not enough

[brandond]

And now you know something new about unix filesystem permissions!

[soupdiver]

And now you know something new about unix filesystem permissions!

You probably too