From f0699232466a59d196c0d8db344b13a791fedf4a Mon Sep 17 00:00:00 2001 From: Jan Smid Date: Tue, 12 May 2026 10:18:50 +0200 Subject: [PATCH] [troubleshooting] Adds ryuk container fail section to troubleshooting Document how to diagnose and fix acceptance test failures caused by the ryuk reaper container being unable to access the Docker socket. Signed-off-by: Jan Smid --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 79746c43c..ced6930f2 100644 --- a/README.md +++ b/README.md @@ -106,6 +106,19 @@ This issue may be resolved by increasing the total number of keys by executing t $ echo kernel.keys.maxkeys=1000 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p ``` +#### **2.4. Ryuk reaper container fails to start** + +Acceptance tests may fail with errors like `No such container` or `unexpected container status "removing"` when the testcontainers' ryuk reaper container cannot access the Docker socket. To diagnose, run ryuk manually in the foreground: +``` bash +$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock testcontainers/ryuk:0.11.0 +``` +If the error is `permission denied while trying to connect to the Docker daemon socket`, create or update `~/.testcontainers.properties` with: +``` +ryuk.container.privileged=true +``` + +This tells testcontainers to run the ryuk container with `--privileged`, granting it access to the Docker socket. + #### **3. Apiserver and Rekor Host Resolution Failure** While running the acceptance tests, you might encounter issues related to apiserver and rekor hosts, like: