Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
FIPS-compliant GitLab images providing a complete DevOps platform that meets Federal Information Processing Standards for cryptographic operations, source code management, CI/CD automation, and collaboration tools.
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 gitlab-fips
images are FIPS-compliant versions based on the upstream GitLab components and are compatible with the official GitLab Helm chart. These images provide all the GitLab components in minimal, secure container images built on Wolfi with FIPS-validated cryptographic modules.
This FIPS-compliant image group includes the following components:
gitaly-fips
- Git repository storage servicegitlab-agent-fips
- GitLab Kubernetes Agentgitlab-base-fips
- Base image with common GitLab functionalitygitlab-certificates-fips
- Certificate management for GitLabgitlab-container-registry-fips
- GitLab's container registrygitlab-exporter-fips
- Prometheus metrics exportergitlab-kas-fips
- GitLab Agent Servergitlab-pages-fips
- GitLab Pages static site hostinggitlab-runner-fips
- GitLab CI/CD runnergitlab-runner-helper-fips
- Helper image for GitLab Runnergitlab-shell-fips
- SSH access to Git repositoriesgitlab-sidekiq-ce-fips
- Background job processing (Community Edition)gitlab-toolbox-ce-fips
- Administrative toolbox (Community Edition)gitlab-webservice-ce-fips
- Main GitLab web application (Community Edition)gitlab-workhorse-ce-fips
- HTTP reverse proxy for GitLab (Community Edition)These images maintain compatibility with the upstream GitLab components while providing enhanced security through minimal design, regular updates, and FIPS 140-3 Level 1 validated cryptographic modules.
These FIPS-compliant images include OpenSSL FIPS provider and are built with FIPS-validated cryptographic modules. Key FIPS features include:
The gitlab-fips
images are designed to work together as a complete FIPS-compliant GitLab deployment using the official GitLab Helm chart. Here's how to configure your GitLab installation to use Chainguard FIPS Images:
Install GitLab using the Helm chart with your FIPS values:
For a development or testing environment, you can combine the above with these minimal settings:
GitLab FIPS components can be configured through the Helm chart values or environment variables. Here are some common configuration scenarios for FIPS compliance:
For the gitlab-shell-fips
component, SSH is automatically configured with FIPS-approved ciphers and algorithms:
Configure GitLab Runner with FIPS-compliant helper images:
Set appropriate resource limits for production environments:
To verify FIPS mode is enabled, you can check the OpenSSL FIPS provider status within any container:
For complete configuration options, refer to the GitLab Helm chart values documentation.
For more information about working with GitLab FIPS and Chainguard Images:
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 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
Artistic-1.0-Perl
BSD-2-Clause
BSD-3-Clause
CC-PDDC
GCC-exception-3.1
GPL-1.0-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs