atlas-fips

packaged by Chainguard

Chainguard Container for atlas-fips

Declarative schema migrations with schema-as-code workflows (FIPS)

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/atlas-fips: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 Container for atlas-fips is the FIPS-mode variant of the atlas Chainguard Container and is intended as a drop-in replacement for the upstream arigaio/atlas image in FIPS-regulated environments. A few security-hardening differences to be aware of when migrating:

• Non-root user. Upstream arigaio/atlas runs as root (User: "0" per crane config); the Chainguard image runs as the non-root user 65532. Bind-mounted migration directories and any files Atlas writes at runtime must be readable (and, for migrate apply/migrate hash, writable) by UID 65532.
• Entrypoint path. To preserve the upstream /atlas entrypoint, the image ships an /atlas symlink that resolves to /usr/bin/atlas (the canonical binary path in the underlying atlas-fips APK). Commands and CI pipelines that invoke /atlas ... continue to work unchanged.
• ATLAS_DOCKER_IMAGE=1 is set in the environment by default, matching upstream behavior so Atlas knows it is running inside a container.

FIPS Support

The atlas-fips Chainguard Container is built with Chainguard's FIPS-validated Go toolchain, so the resulting binary is linked against a FIPS 140-validated cryptographic module. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

Atlas is a database schema management tool that lets you write, plan, verify, and apply schema changes using a declarative HCL syntax or auto-generated migration files.

Print the CLI help:

docker run --rm cgr.dev/ORGANIZATION/atlas-fips:latest --help

Inspect a database schema:

docker run --rm cgr.dev/ORGANIZATION/atlas-fips:latest schema inspect \
  --url "postgres://user:pass@host:5432/db?sslmode=disable"

Apply migrations from a local directory (mounted into the container):

docker run --rm -v "$PWD/migrations:/migrations" cgr.dev/ORGANIZATION/atlas-fips:latest \
  migrate apply \
  --url "postgres://user:pass@host:5432/db?sslmode=disable" \
  --dir "file:///migrations"

Documentation and Resources

• Atlas documentation — the official reference for the CLI, HCL schema syntax, and workflow guides.
• ariga/atlas on GitHub — upstream source, release notes, and issue tracker.

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.