testcontainers / testcontainers/moby-ryuk
[Bug]: container ryuk 0.14.0 is failing to start on ppc64le
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 244
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Module
Core
Testcontainers version
2.0.4
Using the latest Testcontainers version?
Yes
Host OS
Linux
Host Arch
ppc64le
Docker version
no access to the machine
What happened?
the ryuk container is failing to start after upgrade from 2.0.3 to 2.0.4
Relevant log output
org.testcontainers.containers.ContainerLaunchException: Container startup failed for image testcontainers/ryuk:0.14.0
at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:346)
at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
at org.testcontainers.utility.RyukResourceReaper.maybeStart(RyukResourceReaper.java:78)
at org.testcontainers.utility.RyukResourceReaper.init(RyukResourceReaper.java:42)
at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:245)
at org.testcontainers.DockerClientFactory$1.getDockerClient(DockerClientFactory.java:108)
at com.github.dockerjava.api.DockerClientDelegate.authConfig(DockerClientDelegate.java:111)
at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:316)
at org.apache.camel.test.infra.messaging.services.MessagingLocalContainerInfraService.initialize(MessagingLocalContainerInfraService.java:61)
at org.apache.camel.test.infra.common.services.TestServiceUtil.tryInitialize(TestServiceUtil.java:43)
at org.apache.camel.test.infra.common.services.TestService.beforeAll(TestService.java:28)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception
at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:331)
... 11 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:551)
at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:341)
at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
... 12 more
Caused by: java.lang.IllegalStateException: Wait strategy failed. Container is removed
at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:498)
... 14 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*Started.*'
at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:904)
at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:487)
... 14 more
Additional Information
this is happening on a CI machine and I do not have access to a ppc64le machine to investigate further
Contributor guide
No contributing guide indexed for this repository
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 investigating the testcontainers/ryuk:0.14.0 image on ppc64le and compare it with the 2.0.3-to-2.0.4 upgrade boundary. Trace the RyukResourceReaper and GenericContainer startup path shown in the log, then verify that the container reaches the expected “Started” log output on the affected architecture.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100