glibc-dynamic-fips
Glibc-Dynamic-FIPS Overview
Secure your stack with a hardened, FIPS-validated Glibc-Dynamic image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies.
Use this image in a Dockerfile as a secure runtime for dynamically-linked binaries with dependencies (These are listed in the .so file). For example, you can use this image to build a FIPS validated app with the Go-FIPS image.
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
The Glibc-Dynamic-FIPS image can provide an OpenSSL module and runtime for Go-FIPS. In this example, we use the Minimus Glibc-Dynamic-FIPS image as a runtime for a simple web application built with Go-FIPS.
Step 1: Authenticate to the Minimus Registry
Step 2: Create a Dockerfile
In a new project directory, save the code below to a new Dockerfile:
# Pull Go-FIPS image and set it as builder
FROM reg.mini.dev/go-fips AS builder
# Set CGO_ENABLED=1 to compile a dynamically linked binary
ENV CGO_ENABLED=1 GOOS=linux GOARCH=amd64
# Copy the project directory content to app directory in the container
COPY . /app
# Compile Go application
RUN cd /app && go build -o Hello-Minimus-Web .
# Pull dynamic image to use as a runtime base
FROM reg.mini.dev/glibc-dynamic-fips:latest
# Copy Go binary from the /app directory in the builder container to /usr/bin/ in the final dynamic container
COPY --from=builder /app/Hello-Minimus-Web /usr/bin/
EXPOSE 8080
# Set entrypoint to run the binary when the container is started
ENTRYPOINT ["/usr/bin/Hello-Minimus-Web"]A dynamic Go application means it is linked to database drivers or other C integrations. The CGO_ENABLED=1 flag in the Dockerfile is responsible for compiling the Go code using dynamically linked binaries.
Step 3: Download the Sample Code
Download the example file hello-minimus-web.go and save it to your project directory. This is a very simple script that creates a webpage with several tabs so you can navigate between them.
Step 4: Declare Dependencies
In your project directory, create a go.mod file. This file declares the modules and dependencies required by the project. In our case, the module set is only needed for testing purposes, so it's very simple.
module minimus.dev/hello_minimus
go 1.25Step 5: Review Folder Structure
Your project directory should now look like this:
project-root/
├── Dockerfile
├── hello-minimus-web.go
└── go.modStep 6: Build the App
From your project directory, build your custom image. Note that the period . specifies the current directory as the build context:
docker build -t hello-go-web .Step 7: Test the App
Run the final image we just created:
docker run --rm -p 8080:8080 hello-go-webVisit http://localhost:8080/ to see the default welcome page.
Technical Considerations
The Glibc-Dynamic-FIPS image provided by Minimus has no alternative in Docker Hub. It can be used as a minimal alternative for larger images that are used for both compiling the code and running it, for example Golang.
Glibc-Dynamic-FIPS built by Minimus:
- The image can be used as a minimal, secure runtime base for any dynamically-linked glibc binary.
- Runs as non-root by default.
- 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.