gitlab-container-registry-fips

Apps

Fips

Stig

Updated yesterday

GitLab-Container-Registry-FIPS Overview

Secure your stack with a FIPS-validated, hardened GitLab-Container-Registry image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

GitLab Container Registry lets teams store and manage Docker and OCI images alongside their GitLab projects, so pushing and pulling images works with the same repository permissions and CI/CD pipelines already in place, without a separate registry account or access model to manage. It's the registry service GitLab itself runs to power the built-in Container Registry feature on GitLab.com and self-managed instances, and it can also run on its own for deployments that need GitLab-integrated image storage without hosting the rest of GitLab. Use this image when you need to meet the requirements for FIPS-validated cryptographic protection.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

Take the Minimus GitLab-Container-Registry-FIPS image for a test run. The image expects a configuration file at startup, so create a minimal one first. Newer registry versions require a reachable Postgres metadata database on a fresh install, so this example sets database.enabled to false to keep the demo simple:

cat <<EOF > config.yml
version: 0.1
log:
  fields:
    service: registry
storage:
  filesystem:
    rootdirectory: /tmp/registry
database:
  enabled: false
http:
  addr: :5000
EOF

Start the registry, mounting the config file into the container:

docker run --rm -d \
  --name minimus-gitlab-registry \
  -p 5000:5000 \
  -v $(pwd)/config.yml:/etc/docker/registry/config.yml \
  reg.mini.dev/gitlab-container-registry-fips

Verify it's running by querying the registry API:

curl http://localhost:5000/v2/

An empty JSON object {} confirms the registry's v2 API is reachable and healthy.

To push an image to your local registry, pull a small image, tag it for your local registry, and push it:

docker pull reg.mini.dev/hello-world
docker tag reg.mini.dev/hello-world localhost:5000/hello-world
docker push localhost:5000/hello-world

List the images now stored in your registry:

curl http://localhost:5000/v2/_catalog

You should see the image you've added:

{"repositories":["hello-world"]}

Technical Considerations

The GitLab-Container-Registry-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image. The images are largely interchangeable, with a few differences as noted below.

GitLab-Container-Registry-FIPS built by Minimus:

Runs as non-root by default as user 1000 for a security-first approach that protects against privilege escalation attacks.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.