This message was deleted.

I normally run

k3s-killall.sh

this will terminate k3s processes

but then the k3s service is stopped, i need it restarted

I think a normal systemctl stop (or restart) with k3s & rke2 will leave the static containers running and potentially any other cluster containers too. You might need to do a systemctl stop & then k3s-killall.sh and then be able to do a systemctl start without the error?

i have manually tried

systemctl restart k3s

and it solves the issue. My problem is that i can't run that from within a container in the cluster and thus the question. Is there a way to restart k3s from within using something else than

systemctl

or is there a way to use

systemctl

from within container?