You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node(s) CPU architecture, OS, and Version:
Any. Not relevant.
Cluster Configuration:
Various configurations. Not relevant.
Describe the bug:
The generated k3s-killall.sh and k3s-uninstall.sh scripts replace the current process with the same but running with sudo. This does not preserve the environment, i.e. a custom data directory using K3S_DATA_DIR is ignored.
Expected behavior:
Uninstallation should work properly. $K3S_DATA_DIR should be cleaned.
Actual behavior:
Instead of $K3S_DATA_DIR, /var/lib/rancher/k3s is used. $K3S_DATA_DIR is not cleaned. K3s is not properly uninstalled. This can be seen in the logs.
The text was updated successfully, but these errors were encountered:
Environmental Info:
K3s Version:
v1.31.2+k3s1
Node(s) CPU architecture, OS, and Version:
Any. Not relevant.
Cluster Configuration:
Various configurations. Not relevant.
Describe the bug:
The generated
k3s-killall.sh
andk3s-uninstall.sh
scripts replace the current process with the same but running withsudo
. This does not preserve the environment, i.e. a custom data directory usingK3S_DATA_DIR
is ignored.Steps To Reproduce:
K3S_DATA_DIR=$HOME/mydata
k3s-uninstall.sh
in the same shellExpected behavior:
Uninstallation should work properly.
$K3S_DATA_DIR
should be cleaned.Actual behavior:
Instead of
$K3S_DATA_DIR
,/var/lib/rancher/k3s
is used.$K3S_DATA_DIR
is not cleaned. K3s is not properly uninstalled. This can be seen in the logs.The text was updated successfully, but these errors were encountered: