adamant-kite-43734
02/28/2023, 2:27 PMlate-needle-80860
02/28/2023, 3:31 PMsteep-branch-9388
02/28/2023, 3:41 PM<http://test.local.gd|test.local.gd>
which always resolves to localhost. I fixed internal k3s communication with coredns (although https fails).
Problem: my k3s cluster is damaged when I restart itsteep-branch-9388
02/28/2023, 3:43 PMcreamy-pencil-82913
02/28/2023, 5:00 PMsteep-branch-9388
02/28/2023, 5:16 PMsteep-branch-9388
02/28/2023, 5:18 PMsteep-branch-9388
02/28/2023, 5:19 PMcreamy-pencil-82913
02/28/2023, 5:21 PMdocker run rancher/k3s
should work finesteep-branch-9388
02/28/2023, 5:27 PMfailed to evacuate root cgroup: mkdir /sys/fs/cgroup/init: read-only file system
creamy-pencil-82913
02/28/2023, 5:28 PMsteep-branch-9388
02/28/2023, 5:29 PMdocker run rancher/k3s
steep-branch-9388
02/28/2023, 5:29 PM--privileged
works, now i get the error --token is required
steep-branch-9388
02/28/2023, 5:30 PMserver --token
...steep-branch-9388
02/28/2023, 5:31 PMUnable to get btrfs mountpoint IDs
steep-branch-9388
02/28/2023, 5:37 PMcreamy-pencil-82913
02/28/2023, 5:42 PMcreamy-pencil-82913
02/28/2023, 5:43 PMsteep-branch-9388
02/28/2023, 6:02 PMcreamy-pencil-82913
02/28/2023, 6:02 PMsteep-branch-9388
02/28/2023, 6:03 PMcreamy-pencil-82913
02/28/2023, 6:06 PMcreamy-pencil-82913
02/28/2023, 6:06 PMsteep-branch-9388
02/28/2023, 6:06 PMsteep-branch-9388
02/28/2023, 6:08 PMsteep-branch-9388
02/28/2023, 6:09 PMsteep-branch-9388
02/28/2023, 6:11 PMsteep-branch-9388
02/28/2023, 6:11 PMkubectl
will give you a lot of errors
• What causes this issue: it’s a known issue with dqlite in `k3s` which doesn’t allow the initializing server node to go down
• What’s the solution: Hopefully, this will be solved by the planned replacement of dqlite with embedded etcd in k3screamy-pencil-82913
02/28/2023, 6:30 PMcreamy-pencil-82913
02/28/2023, 6:30 PM