Closed lmb closed 8 months ago
There are variations on a theme here. The error I saw was because lb-node
was gone all of a sudden. It seems other containers also just vanish:
+[12:43:45] docker exec -t lb-node docker run --name cilium-lb -td -v /sys/fs/bpf:/sys/fs/bpf -v /lib/modules:/lib/modules --privileged=true --network=host quay.io/cilium/cilium-ci:e8296f91aadc403b3513618771c7b1b6f539056b cilium-agent --enable-ipv4=true --enable-ipv6=true --devices=eth0 --datapath-mode=lb-only --bpf-lb-algorithm=maglev --bpf-lb-dsr-dispatch=ipip --bpf-lb-acceleration=native --bpf-lb-mode=snat
ab9e5fc98340dfb6a69ebebf300bd45af04c6b99a31de37281a4423316e5c6a6
+[12:43:46] docker exec -t lb-node docker exec -t cilium-lb cilium status
Get "http:///var/run/cilium/cilium.sock/v1/healthz": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?
+[12:43:46] sleep 3
+[12:43:49] docker exec -t lb-node docker exec -t cilium-lb cilium status
Error response from daemon: Container ab9e5fc98340dfb6a69ebebf300bd45af04c6b99a31de37281a4423316e5c6a6 is not running
ab9e5fc98340
is cilium-lb, not lb-node
.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has not seen any activity since it was marked stale. Closing.
This happens somewhat regularly:
More complete list: https://github.com/cilium/cilium/actions/workflows/tests-l4lb.yaml?query=is%3Afailure