Skip to content
This repository was archived by the owner on May 15, 2026. It is now read-only.
This repository was archived by the owner on May 15, 2026. It is now read-only.

Support K3S  #60

Description

@abrahamhwj

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions