testcontainers / testcontainers/testcontainers-java
[Bug]: Java k3s testcontainers fails to start in Concourse CI
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the K3S container startup through the Java JUnit test in Concourse CI and inspect the reported logs. Done means the container starts successfully without the missing /dev/kmsg error in that environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- ci-cd, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100