Skip to content

[Bug]: Java k3s testcontainers fails to start in Concourse CI #10125

Open

Description

@agateaux

Module

K3S

Testcontainers version

1.20.4

Using the latest Testcontainers version?

Yes

Host OS

Linux

Host Arch

x86

Docker version

27.5.1

What happened?

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"

Additional Information

No response

Activity

  1. amitdako commented on Nov 18, 2026

    @amitdako

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions