-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No such image: alpine:3.5" error on health check in Fedora 29 with Docker/Moby 18.06.0-dev #1552
Comments
Hey Marcin, so you didn't install Docker using the Docker repository, but instead installed moby (as I assume the problem happens when using this image: testcontainers-java/core/src/main/java/org/testcontainers/utility/TestcontainersConfiguration.java Lines 45 to 47 in 40724a0
Just to be sure (and since I don't know which side effects this switch of Docker engine might have had), could you try to remove your old images and let Docker (by running your Testcontainers code) pull them again? Maybe something with the caching and lookup keys is messed up. Also, do you still have Ryuk disabled in your setup? I think your problem happens here, which is only executed if Ryuk is not running: testcontainers-java/core/src/main/java/org/testcontainers/DockerClientFactory.java Line 136 in ca4505a
|
Thanks Kevin for you suggestion and sorry for delay. I checked it with Ryuk enabled and the health check passes, but the requested container is not found:
The container seemed to be available:
However,
and after that I'm able to run Redis with that container with Testcontainers and Moby. The images not available locally works out-of-box. With Ryuk disable the situation was the same. I needed to try to run the container from a command line to force its download. After that Testcontainers works fine. It would be nice to have Testcontainers download it for me, but it's a rare case, so I'm closing this issue. |
@szpak
It seems that you're running a dev version of Docker, could you please try the latest stable? |
HI all, i was experienced the same issue, i upgraded the test container to the version 1.17.3 and work. |
Fedora 29 provides the quite old patched version of Docker 1.13 and Docker (Moby) 18.06.0-dev (1.38) packaged as moby-engine. With Docker 1.13 it is possible to use different containers using different access methods (JUnit 4 rule, Spock, or
new GenericContainer()
). However, there are some problems with Ryuk (#1356) and 1.13 is quite old. After switching to Docker/Moby 18.06.0-dev I'm no longer able to do anything with Testcontainers.Even simple:
finishes with:
Docker in general seems to work fine:
I can use/run images from the command line.
The full logs with a stacktrace (pointing to some health check operations) with testcontainers and the docker client set to debug:
The text was updated successfully, but these errors were encountered: