You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Java k3s testcontainers fails to start in Concourse CI #10125
When Junit wants to start the container, k3s logs ends with:
Error: failed to run Kubelet: failed to create kubelet: open /dev/kmsg: no such file or directory
time="2025-03-18T01:40:08Z" level=error msg="kubelet exited: failed to run Kubelet: failed to create kubelet: open /dev/kmsg: no such file or directory"
Relevant log output
Error: failed to run Kubelet: failed to create kubelet: open /dev/kmsg: no such file or directory
time="2025-03-18T01:40:08Z" level=error msg="kubelet exited: failed to run Kubelet: failed to create kubelet: open /dev/kmsg: no such file or directory"
Hi! I'd like to look into this issue and submit a PR.
In isolated CI / DinD environments where /dev/kmsg isn't available on the host container, kubelet fails on startup. I'm checking K3sContainer to see how container startup / kubelet arguments are currently configured and will propose a clean fix (e.g., handling missing /dev/kmsg or passing the appropriate kubelet configuration). Let me know if you have a preferred approach!
Activity
amitdako commentedon Nov 18, 2026
Hi! I'd like to look into this issue and submit a PR.
In isolated CI / DinD environments where /dev/kmsg isn't available on the host container, kubelet fails on startup. I'm checking K3sContainer to see how container startup / kubelet arguments are currently configured and will propose a clean fix (e.g., handling missing /dev/kmsg or passing the appropriate kubelet configuration). Let me know if you have a preferred approach!