toxiproxy

packaged by Chainguard

Chainguard Container for toxiproxy

A TCP proxy to simulate network and system conditions for chaos and resiliency testing

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/toxiproxy:latest

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

Compatibility Notes

Unlike upstream ghcr.io/shopify/toxiproxy, which runs as root, cgr.dev/ORGANIZATION/toxiproxy runs as the nonroot user (UID 65532). It keeps the upstream entrypoint /toxiproxy and default argument -host=0.0.0.0. The /toxiproxy and /toxiproxy-cli paths are symlinks to /usr/bin/toxiproxy-server and /usr/bin/toxiproxy-cli. The image is built with Go from upstream release 2.12.0 and sets LOG_LEVEL=info, as upstream does.

Getting Started

Start the Toxiproxy server and its HTTP control API on port 8474:

docker run -d --name toxiproxy -p 8474:8474 \
  cgr.dev/ORGANIZATION/toxiproxy:latest
curl -s http://localhost:8474/version

Create a proxy through the API and publish its listen port. For example, to proxy a Redis server reachable as redis:6379 on the same Docker network:

curl -s -XPOST http://localhost:8474/proxies \
  -d '{"name":"redis","listen":"0.0.0.0:6600","upstream":"redis:6379","enabled":true}'

Add a latency toxic to the proxy:

curl -s -XPOST http://localhost:8474/proxies/redis/toxics \
  -d '{"type":"latency","attributes":{"latency":800,"jitter":0}}'

The bundled CLI is available at /toxiproxy-cli:

docker run --rm --network container:toxiproxy --entrypoint /toxiproxy-cli \
  cgr.dev/ORGANIZATION/toxiproxy:latest list

To deploy with the Delivery Hero community Helm chart, override the image:

helm repo add deliveryhero https://raw.githubusercontent.com/deliveryhero/helm-charts/refs/heads/master/
helm install toxiproxy deliveryhero/toxiproxy --namespace toxiproxy --create-namespace \
  --set image.repository=cgr.dev/ORGANIZATION/toxiproxy \
  --set image.tag=latest

Configuration

• LOG_LEVEL sets the server log level (default info).
• -host and -port set the control API listen address (defaults 0.0.0.0 and 8474). Port 8474 is the exposed control API port; publish each proxy listen port you create as well.
• Proxies to listen on ports below 1024 are not permitted for the nonroot user; use higher ports.

Documentation and Resources

• Upstream repository and documentation
• Toxiproxy is licensed under the MIT License.

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.