Open ecksun opened 2 years ago
It can be started using the provided hint
Hint: enable KubeletInUserNamespace feature flag to ignore the error
~ k3d cluster create --servers 3 --k3s-arg '--kubelet-arg=feature-gates=KubeletInUserNamespace=true@server:*'
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-k3s-default'
INFO[0000] Created image volume k3d-k3s-default-images
INFO[0000] Creating initializing server node
INFO[0000] Creating node 'k3d-k3s-default-server-0'
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-k3s-default-tools'
INFO[0001] Creating node 'k3d-k3s-default-server-1'
INFO[0002] Creating node 'k3d-k3s-default-server-2'
INFO[0002] Creating LoadBalancer 'k3d-k3s-default-serverlb'
INFO[0002] Using the k3d-tools node to gather environment information
INFO[0002] HostIP: using network gateway 10.89.0.1 address
INFO[0002] Starting cluster 'k3s-default'
INFO[0002] Starting the initializing server...
INFO[0002] Starting Node 'k3d-k3s-default-server-0'
INFO[0004] Starting servers...
INFO[0004] Starting Node 'k3d-k3s-default-server-1'
INFO[0023] Starting Node 'k3d-k3s-default-server-2'
INFO[0040] All agents already running.
INFO[0040] Starting helpers...
INFO[0040] Starting Node 'k3d-k3s-default-serverlb'
INFO[0046] Injecting records for hostAliases (incl. host.k3d.internal) and for 4 network members into CoreDNS configmap...
INFO[0048] Cluster 'k3s-default' created successfully!
INFO[0048] You can now use it like this:
kubectl cluster-info
⎈ k3d-k3s-default () ~ k get nodes
NAME STATUS ROLES AGE VERSION
k3d-k3s-default-server-0 Ready control-plane,etcd,master 84s v1.26.4+k3s1
k3d-k3s-default-server-1 Ready control-plane,etcd,master 72s v1.26.4+k3s1
k3d-k3s-default-server-2 Ready control-plane,etcd,master 55s v1.26.4+k3s1
What did you do
What did you expect to happen
I expected to get a working cluster with three nodes
What happened
After trying to start the cluster the startup seem to hang indefinetly after the log line
Starting Node 'k3d-k3s-default-server-1'
. The k3d-k3s-default-server-0 seems to be re-trying some operation forever.Some errors from the logs that might be of interest:
Failed to set sysctl: open /proc/sys/net/bridge/bridge-nf-call-iptables: no such file or directory
Failed to set sysctl: open /proc/sys/net/netfilter/nf_conntrack_max: permission denied
"Failed to create an oomWatcher (running in UserNS, Hint: enable KubeletInUserNamespace feature flag to ignore the error)" err="open /dev/kmsg: operation not permitted"
Screenshots or terminal output
The full log of the two pods are in this gist. Because of github issue limits I could not include the entire logs directly in the issue. I have also removed the time and ts fields from the logs to reduce their size.
k3d-k3s-default-server-0
Which OS & Architecture
Which version of
k3d
Which version of docker