foundry

packaged by Chainguard

Chainguard Container for foundry

Foundry provides Forge, Cast, Anvil, Chisel, and Solar for developing and testing Ethereum smart contracts.

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/foundry: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 foundry image is compatible with the upstream Foundry image. The tools retain their /usr/local/bin paths, and the container runs as the foundry user (UID and GID 1000) with the upstream /bin/sh -c entrypoint.

The image does not include an SSH client. forge install uses HTTPS by default; dependencies that require SSH Git URLs are not supported without adding an SSH client.

The default working directory is /, so use a writable working directory for projects. HOME is /home/foundry; mounted project and cache directories must be writable by UID 1000.

Getting Started

Start a local development node using the command documented in Foundry's Docker guide:

docker run --rm -p 8545:8545 --entrypoint anvil \
  cgr.dev/ORGANIZATION/foundry:latest --host 0.0.0.0

For shell commands, pass a single quoted command string to the default entrypoint. To pass individual tool arguments directly, override the entrypoint as in the Anvil example.

Configuration

For an existing project, mount its directory at /workspace and keep the compiler cache in a named volume:

docker volume create foundry-home
docker run --rm \
  --mount type=bind,source="$(pwd)",target=/workspace \
  --mount type=volume,source=foundry-home,target=/home/foundry \
  --workdir /workspace \
  cgr.dev/ORGANIZATION/foundry:latest 'forge build && forge test'

The project directory must be writable by UID 1000 so Forge can create its build output and cache. Use the project's foundry.toml to configure compiler and test settings.

Solidity compiler downloads

Like upstream, the image does not preinstall the Solidity compiler.

Forge may download the Solc executable selected by the project's configuration on first use. This runtime-downloaded executable is supplied by the upstream Solidity compiler distribution, not built or provided by Chainguard, and is not part of the published image's SBOM or signature. Environments that require only Chainguard-provided executables should add Chainguard's solc package to the image and configure Forge to use that compiler, or provide another approved compiler and run Forge in offline mode.

Compiler downloads require HTTPS access. Persist /home/foundry to reuse downloaded compilers and caches. See Foundry's compiler configuration for selecting a compiler path or version and using offline mode.

Documentation and Resources

• Foundry documentation
• Anvil reference
• Forge reference

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.