packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Minimalist Wolfi-based image for running the OpenCode AI coding agent as a CLI or as an HTTP API server.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
The opencode image provides a containerized version of OpenCode, an AI coding agent for the terminal, with the following characteristics:
serve HTTP API only — the embedded web console is intentionally not bundled, to keep the image small and the CVE surface low. If you need the web UI, run it as a separate image built on top of the upstream vite/solid-start assets.The entrypoint is the opencode binary at /usr/bin/opencode, built from source from github.com/anomalyco/opencode. Runtime dependencies (bash, git, ripgrep) are already pulled in by the opencode APK and are available inside the image, along with ca-certificates-bundle for TLS to model providers such as api.anthropic.com and api.openai.com.
OpenCode is an AI-powered coding agent that runs in your terminal or as an HTTP API server. To use it, you'll need an API key for your preferred model provider (Anthropic, OpenAI, etc.).
The image runs as the nonroot user (UID 65532), which cannot write to / or an unset $HOME. Mount a writable directory and point HOME, XDG_CONFIG_HOME, and XDG_DATA_HOME at it so OpenCode can persist its config and state.
Set your provider API key as an environment variable and run the container:
Use the serve subcommand to expose OpenCode's HTTP API:
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:
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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.
Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
BSD-3-Clause
GCC-exception-3.1
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.0-or-later
LGPL-2.1-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at Chainguard