ruby-fips
Ruby-FIPS Overview
Secure your stack with a hardened, FIPS-validated Ruby image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies.
Use this Ruby-FIPS 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
We will perform two tests on the Minimus Ruby image. In the first, we will run a Ruby script directly inside a container. In the second, we will build a custom container image using a Dockerfile.
To begin, save the following two files to your project directory:
- Sample script named
containers.rb. Link to file - Sample content file named
containers.txt. Link to file
Your project directory should now look like this:
project-root/
├── containers.txt
└── containers.rbNext, run the script directly in the Ruby container. This command will start the Ruby container and print a random fact from the containers.txt file.
docker run -it --rm \
--name ruby-script \
-v "$PWD":/work -w /work \
reg.mini.dev/ruby-fips \
ruby containers.rbNext we will use a Dockerfile to build our custom image. Save the following as a Dockerfile in your project directory:
FROM reg.mini.dev/ruby-fips:latest
WORKDIR /work
COPY containers.rb containers.txt ./
ENTRYPOINT [ "ruby", "containers.rb" ]Next, build the custom image and run it. Note that the period . specifies the current directory as the build context:
docker build . -t minimus-ruby-demo
docker run --rm minimus-ruby-demoYour container should print a random fact about containers from the containers.txt file.
About Gemfiles
To use a Gemfile with third-party extensions, you will need to use a dev image (for example, ruby:latest-dev) and a multi-stage build. To optimize security, it is recommended to use the Ruby dev image for the build stage and the production Ruby image to run the app.
Technical Considerations
The Ruby-FIPS image provided by Minimus is a FIPS validated, slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.
Ruby-FIPS built by Minimus:
- Runs as non-root by default (user 1000) for a security-first approach that protects against privilege escalation attacks. The public image runs as 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.