docker pull cgr.dev/chainguard/static
Need access to a specific version? Contact us.
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign inBase images with the minimum contents needed to run static binaries.
The image is available on cgr.dev
:
On July 15, 2024 the static:latest
image will move from a Alpine base to a Wolfi base,
in-line with all other images in our registry. We do not expect this to cause breakages, but
encourage all users to test and verify the new version.
You can test today by migrating to the cgr.dev/chainguard/static:latest-glibc
image. From July 15, the :latest
and :latest-glibc
will point to the same image.
Full details are in this blog post.
Chainguard's static Images are meant to be used as a base image only and are not intended to be run directly.
There are two variants of the static Image available: latest
, which contains base OS files from
Alpine and latest-glibc
which contains base OS files from
Wolfi. These variants are largely equivalent and can be used to host completely static binaries, such as those generated by gcc
, rust
, or go
. Be aware that there is no libc implementation in either Image, despite the naming convention.
If you need images with the C standard library included, check out Chainguard's glibc-dynamic Image.
This Image has a single user nonroot
with uid 65532
, belonging to gid 65532
.
The static image is not versioned, since there's hardly any software in it that has a useful version. Most updates to the image are due to routine rebuilds of the packages included in the image, and don't constitute any functional change.
In general it should be safe to rely on the :latest
or :latest-glibc
tag, but you may also want to pin the image reference by digest and use a tool like digestabot to automate image digest updates.
This section outlines how to build a Rust static binary with Chainguard's static Image. First, create a Dockerfile named Dockerfile.rust
with your preferred text editor.
Then add the following instructions to the file, which build a Rust static binary and put it into the static Image:
Save and close the file. To build the binary, run the following command:
This command tags the binary with rusty-cgr
. You can run this newly-built Image with the following command:
If you inspect this image, you'll find that it has a relatively small size:
This section is similar to the previous one, but instead outlines how to build a C static binary. This time, create a Dockerfile named Dockerfile.c
with your preferred text editor:
Add the following instructions to the file:
After saving and closing the Dockerfile, you can build the binary:
Then run it by referencing the tag c-cgr
:
Inspect this newly-built image as well.
This C static binary is even smaller than the Rust one built in the previous section.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
CC-PDDC
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementProducts
Chainguard Images© 2024 Chainguard, Inc.