Kyle Sanderson

Any update on this? ``` Downloading Packages: (1/9): k3s-selinux-1.1-1.el8.noarch.rpm 33 kB/s | 20 kB 00:00 (2/9): container-selinux-2.188.0-1.el9_0.noarch.rpm 243 kB/s | 47 kB 00:00 (3/9): python3-setools-4.4.0-4.el9.x86_64.rpm 478 kB/s | 547 kB...

Same time.

From what I'm seeing (I'm only like 3 hours into code - so pretty fresh) it looks like this is never a safe operation if there are any clients connected....

Yeah - even with 10 failures it still doesn't go well. The shutdown ever finishes either. ``` I0112 08:23:09 1 common.go:105] error writing JSON status 200: write tcp 10.0.0.17:8081->10.0.0.172:51198: write:...

> Some more context? Could not tell much just from logs. I have a liveness probe querying the status endpoint on the volume server every 3 seconds as there's no...

It's a fairly small amount, around 100 volumes. Feels pretty silly honestly.

I've gotten Cilium running in pure eBPF mode. I had to hack the k3d filesystem again though. ``` Warning Failed 47s kubelet Error: failed to generate container "d188af429270e2234add1b3d0506ca07f9fe82cdef73da381c70014d941ca175" spec: failed...

@iwilltry42 it's pretty simple to fix, docker exec into the container and run `mount --make-rshared /`. Super annoying to have to do this **every** reboot.

Any update on this critical for usage issue?

@iwilltry42 is there anything I can do to help on this critical issue.