"No such image: testcontainers/ryuk:0.3.0" #3574
Comments
|
@gesellix do you have a mirror configured? Or is this a response from Docker Hub? |
|
I suppose that the 404 is the local Docker Engine and no lookup to any registry is made. In this case I don't use any private registry, the engine is directly connecting to the Docker Hub. Manual |
|
As far as I know the docker cli had some logic like this for I don't understand, though, why we now run into such an issue. The only thing I'm aware of is docker/cli#1498, which might be related. |
|
Did/does Testcontainers pull images, in this case ryuk, before trying to create containers? |
|
I'm hitting this today too. In my case, for a Postgres container. I tried setting The other thing I suspected was maybe we're hitting the Docker Hub pull limits? I thought since this is communicating with the daemon it should use the auth configured on the host, but possibly I'm misunderstanding. |
|
... so maybe the pull for ryuk is performed unauthenticated? |
|
That's what I was worried about, yea. But I'm not sure if that's what's going on or not yet. |
|
@gesellix we definitely pull the image if it is not available.
In that case, an error would differ (unless the Docker Hub team have decided that |
|
When we got the error before, from running docker commands directly in a job, we got a message that specifically said we hit pull limits. But I don't know the HTTP status that the docker binary received in that case, so I wasn't sure if the message was possibly being hidden by TestContainers or not. |
|
While our GitHub Actions still work (same Testcontainers version, but differend Docker Engine/operating system), I guess this is mainly related to Docker for Mac. I can give it a try with an older Docker4Mac release tomorrow. |
|
In my case, it's passing locally on Mac with latest Docker for Mac stable (but I have those images in my cache though) and failing on GitLab. |
|
404 and Also, |
|
oh wait, I think I know what is it... |
|
Well, that rules out that possibility then, at least. Maybe Docker Hub is having some problem? I just tried disabling ryuk and then it said 404 with |
|
For me Docker Hub seemed to be ok, |
|
Good point. |
bsideup
added a commit
that referenced
this issue
Dec 9, 2020
|
Ok, "filter by image name" query parameter in I just submitted #3575 with a fix, will be included in 1.15.1 |
|
I suppose I should mention too that I had tried with 1.15.0-rc2 and 1.15.0. |
Ah, so a change in Docker Hub API? I deleted ryuk image locally and ran test again, oddly passed again. |
|
@keeganwitt Docker's API. Although the query param was deprecated (I wish we could run Docker in a strict API mode - will explore) Sorry for this. We will release a hotfix ASAP. Meanwhile, consider pre-pulling |
Yea, I'd thought of that, but I'm not sure it's possible with GitLab's Docker Executor. It should be possible to run it as a script with shell executor instead though I suppose. I'm still confused why it worked locally after deleting the ryuk image though... Maybe different Docker daemon versions? |
|
Thanks @bsideup for the quick fix! |
|
Are you planning to backport this to work also with junit 4? |
|
@DaspawnW this is not junit specific and, once released, will work with any type of integration (junit4, junit jupiter, spock, manual container lifecycle) |
|
@keeganwitt did you ever find a reasonable workaround for builds running in Gitlab? We have been looking at this for a day now without much success. It works if you manually pre-pull the images, but we are using docker-machine to autoscale the runners in EC2, so manual work is not really an option. |
bbednarek
pushed a commit
to VivyTeam/spring-boot-starter-liiklus
that referenced
this issue
Apr 23, 2021
bbednarek
pushed a commit
to VivyTeam/spring-boot-starter-liiklus
that referenced
this issue
Apr 23, 2021
* MAIN add dependabot and gradle update github actions * update test containers due to testcontainers/testcontainers-java#3574 * fix the maven repos * bring back jcenter
Malinskiy
pushed a commit
to MarathonLabs/marathon
that referenced
this issue
Apr 27, 2021
|
Hi. It seems that this error is happening again.
It's failing with the same error: I've tried to downgrade Docker Desktop and it was failing until Docker Desktop Community 2.5.0.1, which is using Docker engine 19.03.13. So with this last version (and keeping the same Testcontainers versions) is working. Also, I've applied the workaround of manually downloading the image So please, if someone else is facing the same problem, maybe it's worth to have a look if something has broken with this last Docker version. Thank you! |
|
@MiguelAngel82 Testcontainers 1.15.3 depens on Ryuk 0.3.1, meaning that you're still using an older version of Testcontainers |
Malinskiy
added a commit
to MarathonLabs/marathon
that referenced
this issue
Apr 27, 2021
* ci(ci): migrate to GH Actions * fix(ci): need to upgrade test containers see testcontainers/testcontainers-java#3574 * fix(ci): temporarily allow detekt failures
|
@bsideup Thank you for your response! Sorry, it was my fault. Thanks to your response I've dug deeper into the project and I've realised that we were using another Testcontainers dependency, Thank you and I apologise for the inconvenience. |
lucaspwbx
added a commit
to lucaspwbx/goos
that referenced
this issue
Jun 30, 2021
testcontainers/testcontainers-java#3574 (comment) avoid ryuk image problem
eitsch
added a commit
to eitsch/jfr-custom-events
that referenced
this issue
Jul 8, 2021
ilosamart
added a commit
to oibaf-ifrs/tpack
that referenced
this issue
Jul 22, 2021
- troca parâmetros estáticos no Liberty por variáveis: https://openliberty.io/docs/21.0.0.6/reference/config/server-configuration-overview.html#variable.html - corrige problema no testcontainers: testcontainers/testcontainers-java#3574
gschueler
added a commit
to rundeck/rundeck
that referenced
this issue
Aug 2, 2021
fix build issue testcontainers/testcontainers-java#3574
mzyromski-atlassian
added a commit
to mzyromski-atlassian/jira-software-actions
that referenced
this issue
Oct 26, 2021
testcontainers v1.15.1 is forced to have a version with testcontainers/testcontainers-java#3574 fixed. That required manually resolving net.java.dev.jna:jna version conflict resolution.
mzyromski-atlassian
added a commit
to atlassian/jira-software-actions
that referenced
this issue
Oct 26, 2021
testcontainers v1.15.1 is forced to have a version with testcontainers/testcontainers-java#3574 fixed. That required manually resolving net.java.dev.jna:jna version conflict resolution.
I also has the erro, update the org.testcontainers jar version in maven pom.xml, then fixed! |
kenhtanaka
added a commit
to cedardevs/onestop
that referenced
this issue
Dec 18, 2021
erinreeves
pushed a commit
to cedardevs/onestop
that referenced
this issue
Jan 6, 2022
erinreeves
pushed a commit
to cedardevs/onestop
that referenced
this issue
Jan 6, 2022
erinreeves
pushed a commit
to cedardevs/onestop
that referenced
this issue
Jan 7, 2022
dvsp-iodigital
added a commit
to foreach-across/across-framework
that referenced
this issue
Dec 20, 2023
…iners/ryuk:0.3.0" error: testcontainers/testcontainers-java#3574 which is fixed in 1.15.1 actually: testcontainers/testcontainers-java#3575 The upgrade to 1.18.1 also required changes the Oracle JDBC URL's in across-bamboo-specs. It was just replacing '@//' with '@'. See: https://shekhargulati.com/2019/01/22/solution-ora-12514-tnslistener-does-not-currently-know-of-service-requested-in-connect-descriptor/
arunbear
added a commit
to arunbear/goos
that referenced
this issue
Oct 4, 2024
With the current version of Docker i.e.
% dockerd -v
Docker version 27.3.1, build 41ca978
end to end tests fail with the message below:
[ERROR] com.belano.auctionsniper.xmpp.XMPPAuctionHouseTest Time elapsed: 0.019 s <<< ERROR!
org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=goos/openfire:latest, imagePullPolicy=DefaultPullPolicy())
Caused by: java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration
This is fixed by updating testcontainers to a newer version.
See also
testcontainers/testcontainers-java#3574 (comment)
|
I'm experiencing the following error, which looks very similar. The first time the Postgres container downloads and starts correctly. Sometimes (not always) the second time it starts, the error message appears. The error (often) occurs repeatedly on the build server, but it can't be reproduced 100%. Second time in the same build. Anyone have any idea how this could happen? And why it only happens sometimes? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testcontainers 1.15.0 on Docker Engine 20.10/Docker for Mac 2.5.4 fails with the following stacktrace:
The text was updated successfully, but these errors were encountered: