moby-ryuk

packaged by Chainguard

Chainguard Container for moby-ryuk

Container resource reaper for Testcontainers — prunes labeled Docker resources after the last client disconnects.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/moby-ryuk:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard moby-ryuk container image is a drop-in replacement for the upstream testcontainers/ryuk Docker Hub image used by the Testcontainers libraries to reap containers, networks, volumes, and images left behind by test runs.

The image runs as non-root (uid 65532) with primary gid 0. Upstream runs as uid 0; the gid 0 membership lets the nonroot process read and write /var/run/docker.sock, which Docker creates as root:root mode 0660.

Getting Started

Ryuk is normally launched automatically by a Testcontainers client library, not run manually. The library spawns a reaper container with the Docker socket mounted, registers cleanup filters over the TCP protocol, and lets the reaper prune matching resources when the test process exits. Disabling the reaper is done with the TESTCONTAINERS_RYUK_DISABLED=true environment variable on the client, not on this image.

To start Ryuk manually (for example, to debug its lifecycle against a local Docker daemon):

docker run -d --name ryuk \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -p 8080:8080 \
  cgr.dev/ORGANIZATION/moby-ryuk:latest

Documentation and Resources

• Moby Ryuk Source Repository
• Testcontainers Documentation
• Testcontainers — Customizing the Ryuk Resource Reaper
• Testcontainers Host Configuration

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.