-
Notifications
You must be signed in to change notification settings - Fork 142
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
Support testcontainers/ryuk
as resource reaper
#577
Comments
We could also think about keeping watchdog for those who can't use ryuk, because of some constraints (e.g. using podman in rootless mode), or even make it the default if ryuk is not enabled. Or just provide both it behind features and the users can choose by themselves whether they want to use ryuk or watchdog. WDYT? |
In general, I like the idea to keep both. But I guess we need to extend watchdog to allow registration of networks (and named volumes?) to make it enabled by default. For now it works only for containers. Anyway, I think |
testcontainers/ryuk
as resource reaper (deprecate watchdog
)testcontainers/ryuk
as resource reaper
Based on observation, localstack containers weren't being shutdown properly. It turns out static bindings don't get shut down, so we need testcontainers/testcontainers-rs#707 (comment) unti testcontainers/testcontainers-rs#577. Signed-off-by: lloydmeta <[email protected]>
Based on observation, localstack containers weren't being shutdown properly. It turns out static bindings don't get shut down, so we need testcontainers/testcontainers-rs#707 (comment) unti testcontainers/testcontainers-rs#577. Signed-off-by: lloydmeta <[email protected]>
Support https://hub.docker.com/r/testcontainers/ryuk as resource reaper, under separate feature
ryuk
The text was updated successfully, but these errors were encountered: