Skip to content
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

Support K3S #60

Open
abrahamhwj opened this issue May 31, 2024 · 0 comments
Open

Support K3S #60

abrahamhwj opened this issue May 31, 2024 · 0 comments

Comments

@abrahamhwj
Copy link

OS version: centos 7.9
K3S version:v1.29.5+k3s1

After I installed the kwasm-operator, the runtime did not take effect. I needed to manually restart k3s. After inspecting some of the code, I found that the problem may be due to the script of our project.

In my installation environment, K3S is installed by default at /usr/local/bin/k3s. This causes the current version of the restart script to fail to restart K3S successfully. Perhaps the following content can be added to the script to solve this, but I apologize as I do not currently have a suitable test environment to test it.

elif ls $NODE_ROOT/usr/local/bin/k3s > /dev/null 2>&1 ; then
    nsenter --target 1 --mount --uts --ipc --net -- /bin/systemctl restart k3s
    nsenter --target 1 --mount --uts --ipc --net -- /bin/systemctl restart k3s-agent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant