testcontainers / testcontainers/testcontainers-java
[Bug]: Testcontainers-Java failing in Jenkins Agent running as a pod in kubernetes with docker sock mounted
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Module
Core
Testcontainers version
latest
Using the latest Testcontainers version?
Yes
Host OS
Linux
Host Arch
x86
Docker version
19.03.13-ce
What happened?
Testcontainers-Java failing in Jenkins Agent running as a pod in kubernetes with docker sock mounted to jenkins agent. My build are failing at test execution in java apps using this test containers
Relevant log output
No response
Additional Information
[Bug]: Testcontainers-Java failing in Jenkins Agent running as a pod in Kubernetes with docker sock mounted
Error:
ViolatorControllerGetViolatorsMetadataIntTest > initializationError FAILED
14:32:39 java.lang.ExceptionInInitializerError at NativeMethodAccessorImpl.java:-2
14:32:39 Caused by: com.github.dockerjava.api.exception.NotFoundException at DefaultInvocationBuilder.java:241
14:32:39
14:32:39 ViolatorControllerGetViolatorsByAlertIntTest > initializationError FAILED
14:32:39 java.lang.NoClassDefFoundError at NativeMethodAccessorImpl.java:-2
14:32:40
14:32:40 AlertControllerGetAlertsMetadataIntTest > initializationError FAILED
14:32:40 java.lang.NoClassDefFoundError at NativeMethodAccessorImpl.java:-2
14:32:40
14:32:40 AlertControllerGetAlertsByViolatorIntTest > initializationError FAILED
14:32:40 java.lang.NoClassDefFoundError at NativeMethodAccessorImpl.java:-2
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 failure in the Jenkins Kubernetes agent with the Docker socket mounted, using Docker 19.03.13 on Linux. Inspect initialization failures in the listed ViolatorController and AlertController integration tests; done means these tests no longer fail with ExceptionInInitializerError or NoClassDefFoundError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, kubernetes
- Domain
- devops, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100