Skip to content

[troubleshooting] Add ryuk troubleshooting section to README #3298

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.

Sign up for GitHub

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

Merged
jsmid1 merged 1 commit into from
Jul 16, 2026
Merged

[troubleshooting] Add ryuk troubleshooting section to README #3298

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Comment thread
jsmid1 marked this conversation as resolved.
$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock testcontainers/ryuk:0.11.0
Comment thread
jsmid1 marked this conversation as resolved.
```
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
Comment thread
jsmid1 marked this conversation as resolved.
```

This tells testcontainers to run the ryuk container with `--privileged`, granting it access to the Docker socket.

Comment thread
jsmid1 marked this conversation as resolved.
#### **3. Apiserver and Rekor Host Resolution Failure**

While running the acceptance tests, you might encounter issues related to apiserver and rekor hosts, like:
Expand Down
Loading