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
tests stopped working on Docker desktop #399
Comments
What is a Ryuk and why should it be running at localhost:32768? |
Oh, wait, I just found this: testcontainers/testcontainers-java#3241 |
PosgreSQL recently released version 13, so I reconfigured our test images to use image Weird, it's supposedly no different from fetching the previous versions. |
I think—but I'm not sure—that I already had it working on Postgres 13 up until I updated Docker. |
First time I hear about Seems a bug in Testcontainers. You might be able to workaround it by downloading the container once manually? try
|
Changing to testcontainers 1.15.0-rc2 seems to have fixed it for me. |
Cool. |
Yep, that worked. Is there a right way to set an environment variable from the gradle script? |
Apparently:
|
right, that should do it. BTW please hold on pushing for some minutes :) release is running |
Release done.. I'll do the Quarkus updates now. |
Excellent! |
Is this still an issue? |
I believe the bug is still there, but the only people who are going to experience it are people who don't already have the thing fetched to their local machine. |
So I wonder if this was caused by the need to upgrade the test database when migrating from Postgres 12 to 13? See, I have |
I don't believe we strictly need that upgrade to PostgreSQL 13 ? AFAIR when I upgraded it I didn't need to make any related changes, so I'd expect everything to work fine on 12 as well - unless a regression was included in the meantime but that seems less likely than having some problems with docker/testcontainers. |
Maybe try to revert the configuration to 12 and see? |
I'm experiencing this again :-(
I set it to false, and it didn't fix the problem. |
This fixed it again. @Sanne Do you think I should push this change to the gradle script? |
yes, sure why not. It seems to be a new feature, and we've been happy so far without it. |
It is actually responsible for terminating the containers after running the tests. If you kill the JVM, the shutdown hooks won't get executed and the containers will continue running, creating dangling containers. tl;dr: do not disable Ryuk ;) |
Well, TBH, I run with And, on balance, dangling containers is less worse than my tests just not running. :-) But sure, if this is fixed in 1.15 (which just came out two days ago, I think) then that's great, and we'll just upgrade instead. |
Thanks for explaning that @bsideup ! |
I've no idea what's going on here, but it seems to have coincided with me updating Docker desktop on Mac to the latest version:
Any ideas @Sanne, @DavideD ?
The text was updated successfully, but these errors were encountered: