K3S Rootless mode daemon-reload : Failed to connect to bus: No such file or directory

[the1bit]

Environmental Info:
K3s Version: latest

Node(s) CPU architecture, OS, and Version: GitHub Action Ubuntu-latest

Cluster Configuration: Single instance

Describe the bug:

• I want to use K3S in a GitHub Action in Rootless-mode.
• I created the ~/.local/bin/k3s and download the k3s with this command: curl -sfL https://get.k3s.io -o ~/.local/bin/k3s
• I created the ~/.config/systemd/user then I downloaded the k3s-rootless.service into it.
• I also modified the k3s-rootless.service with this sed -i 's|ExecStart=/usr/local/bin/k3s server --rootless|ExecStart=/home/runner/.local/bin/k3s server --rootless|' ~/.config/systemd/user/k3s-rootless.service
• Finally I run systemctl --user daemon-reload to reload the daemon.
• Error message: Failed to connect to bus: No such file or directory

Steps To Reproduce:

• Installed K3s: Failed to connect to bus: No such file or directory

Expected behavior:

K3S runs in rootless-mode

Actual behavior:

When I run systemctl --user daemon-reload to reload the daemon. I am facing the following error: Failed to connect to bus: No such file or directory

Additional context / logs:

No additional logs or contexts.

[brandond]

That's an error from systemctl, not k3s. I'm not sure what to suggest, I would probably check the systemd docs.