Replies: 1 comment 1 reply
-
The container must be privileged, and allowed to write to these profcs paths. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Before start
This issue a little bit too specific situations. If not accepting
such kind issue I will move this to Discussions.
Environmental Info:
K3s Version: k3s version v1.30.5+k3s1 (9b58670) go version go1.22.6
Node(s) CPU architecture, OS, and Version:
Linux develop 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux
debian 12
Cluster Configuration:
Single node
Describe the bug:
K3s not working in container ( systemd-nspawn based )
Steps To Reproduce:
Start with brand new Debian 12 minimal install ( Expert install only base system )
Prepare a rootfs
curl -sfL https://rancher-mirror.rancher.cn/k3s/k3s-install.sh | INSTALL_K3S_MIRROR=cn sh -
Expected behavior:
A working K3s
Actual behavior:
K3s install script will stuck at
[INFO] systemd: Starting k3s
Additional context / logs:
Log of
k3s server --debug
, Full log too longIt says
ReadOnly
, But here is mount.I have done some research with container in container, But those posts seems like no helping:
Beta Was this translation helpful? Give feedback.
All reactions