fix(ci): re-enable Testcontainers Ryuk to stop the backend fork shutdown hang (#848) #849

Merged
marcel merged 2 commits from devops/issue-848-fork-exit-timeout into main 2026-06-15 20:53:59 +02:00
Showing only changes of commit 0f9e8c75cc - Show all commits

View File

@@ -229,9 +229,14 @@ jobs:
name: Backend Unit Tests
runs-on: ubuntu-latest
env:
DOCKER_API_VERSION: "1.43" # NAS runner runs Docker 24.x (max API 1.43); Testcontainers 2.x defaults to 1.44
# CI runs against the root-server Docker daemon (29.x). This API pin is a harmless
# carry-over from the old NAS runner (Docker 24.x, max API 1.43); safe to drop later.
DOCKER_API_VERSION: "1.43"
DOCKER_HOST: unix:///var/run/docker.sock
TESTCONTAINERS_RYUK_DISABLED: "true"
# Ryuk (Testcontainers' out-of-process reaper) is intentionally LEFT ENABLED so it
# removes each run's containers after the JVM exits. Disabling it forced the in-JVM
# reaper, which hung at JVM shutdown and leaked Postgres containers run-over-run until
# the daemon degraded and the fork timed out at teardown — see #848.
steps:
- uses: actions/checkout@v4