You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 ryuk should be implemented under separate feature ryuk, so we can keep watchdog and extend separately
DDtKey
changed the title
Support testcontainers/ryuk as resource reaper (deprecate watchdog)
Support testcontainers/ryuk as resource reaper
Apr 25, 2024
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: