https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
n
/usr/local/bin/k3s agent
looks different from 
k3s-agent
t
yeah... exactly
k3s-agent isnt the actual executable installed... its the wording of the error though
k3s is the executable.. agent is the argument. i have no idea why the error lessage is 
k3s-agent
ive inspected the systemd uni... it doesnt references 
k3s-agent
as the executable name, that's something internal in the compiled go executable
the fact that I'm getting it to work as root gives me hope I can sort it out... but its...weird..
n
check this
t
nope the directory stuff is fine.. like i siad.. i can run it as root no problem
root from a terminal
n
t
fstab is clean.... I basically have 2 nucs setup the same way.. one is acting as k3s server... no problem installing there.. other is acting as additional node.
c
How exactly did you install that? It sounds like it failed to extract out the actual binaries
t
no it extracted.. i can run k3s agent as root in a terminal
its just from t he systemd unit where its falling over... really weird
c
if you look in 
/var/lib/rancher/k3s/data/current/bin
there should be a bunch of stuff there, including k3s-agent
t
tons of stuff
im applying updates... this could be a weird selinux thing maybe
c
Copy code
brandond@seago:/$ ls -la /var/lib/rancher/k3s/data/current/bin/k3s-agent
lrwxrwxrwx 1 root root 3 Jul 14 16:22 /var/lib/rancher/k3s/data/current/bin/k3s-agent -> k3s
t
Copy code
ls -la /var/lib/rancher/k3s/data/current/bin/k3s-agent
lrwxrwxrwx. 1 root root 3 Aug 16 15:39 /var/lib/rancher/k3s/data/current/bin/k3s-agent -> k3s
c
and the same for 
/var/lib/rancher/k3s/data/previous/bin/k3s-agent
and neither of those symlinks are broken?
r
It says not found in the path, so that could've gotten garbled?
t
ive no previous directory
c
ok. if this is a fresh install then that’s expected
t
right super fresh
two nucs... the first one acting as a server... no problems
c
is there anything weird about the systemd unit file itself? Did it get garbled by passing through some args or something?
t
i mean... it looks fine... the exec is only /usr/local/bin/k3s agent If i run that with the environment variables set... in a root terminal.. works like a charm
its gonna end up being an selinux enforcing thing... bet you a doughnut
✅ 1
r
Did you install the policy package? I guess I don't know if k3s has one but RKE2 did. It'd set your directory contexts for things like /var/lib/rancher ?
t
installer does that for me
r
Ah, last time I was trying it was as RKE2 was just barely getting out of tech preview for having SELinux enforcing, so some of that wasn't as automatic at that point.
t
im applying updates and rebooting now... and retesting..then ill set to permissive and retest again.
r
Did you do an autorelabel for the reboot too?
t
ill will as soon as updates are done to make sure it runs
reboot fixed it
tis a mystery
lets see if i can see evidence in the audit log
r
If it was the directory label you may see it in audit log, but if it was an install glitch that the update fixed then probably not.
t
the update was for system packages
could have been somethng glitchy that an update fixed..who knows
definitely seeing some k3s / runc avc denials
the nuc operating as k3s server doesnt have any of this.. so im chalking this up to selinux enforcing weirdness
r
I'm not sure with K3S, install, but with RKE2 install it defaulted to RPM and added the yum repos so I did once hose myself a bit with not realizing I was updating my RKE2 version when I was just doing OS patches. Granted, if you installed today probably no K3S updates yet, but I bet if you check your yum repos you'll spot K3S got added.
143 Views
Open in Slack
PreviousNext
Powered by