[troubleshooting] Add ryuk troubleshooting section to README

[jsmid1]

Summary

• Add troubleshooting entry for ryuk reaper container failures in acceptance tests
• Documents how to diagnose the issue by running ryuk manually and how to fix it via ~/.testcontainers.properties

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 9e7360cd-0a81-4c9f-a79f-e67765067d54

📥 Commits

Reviewing files that changed from the base of the PR and between f678eda and f069923.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

A new troubleshooting subsection is added to the README documenting Docker socket access issues with the testcontainers ryuk reaper container. It provides diagnostic commands and explains how to enable privileged mode via the ryuk.container.privileged=true configuration property.

Changes

Ryuk Reaper Troubleshooting Documentation

Layer / File(s)	Summary
Ryuk reaper Docker socket troubleshooting README.md	New subsection 2.4 explains ryuk container startup failures, provides a foreground docker run command for diagnostics, and documents the ~/.testcontainers.properties configuration flag (ryuk.container.privileged=true) to resolve the issue.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: adding a ryuk troubleshooting section to the README.
Description check	✅ Passed	The description is directly related to the changeset, documenting the ryuk troubleshooting entry including diagnosis and fix instructions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}