Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpChainguard 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 python-fips
Chainguard Image provides a FIPS-enabled Python runtime suitable for workloads such as web applications, CLI utilities, interfacing with APIs, or other tasks.
Where possible, the python-fips
Chainguard Image is built for compatibility with the Docker official image for Python.
The python-fips
Chainguard Image ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy
By default, the python-fips
Chainguard Image runs as a non-root user. You may need to use USER root
to perform tasks requiring elevated privileges.
The entrypoint for the python
Chainguard Image is /usr/bin/python
. Commands run as part of docker run
or a CMD
statement in a Dockerfile will be passed as arguments to python
.
We have two image variants available:
python-fips:latest-dev
variant that contains the pip
and apk
package managers and the bash
, ash
, and sh
shells.To pull the minimal runtime variant from cgr.dev
:
To pull the dev variant:
The MD5 algorithm is commonly used to verify data integrity. According to the FIPS framework, MD5 is not suitable for applications like SSL certificates or digital signatures that rely on collision resistance for digital security. Since MD5 is not approved under the FIPS framework, we can test for FIPS compliance by attempting to use this algorithm. This should resultin an error.
First, create a project folder for our test:
Next, create a Python script that attempts to use the MD5 algorithm:
Create a Dockerfile for our image build:
Build the image:
Finally, run the test:
This should produce output similar to the following:
Since MD5 isn't supported in our FIPS-enabled container, we receive an error when attempting to use this algorithm. If you see the above error, the test was successful.
The following provides an example of a CLI application that does not require additional Python dependencies.
First, create a project folder for the example and change the workingdirectory to that folder:
Next, create the Python script:
Create a Dockerfile for our image build. (Make sure to replace the value of the ORGANIZATION environmental variable with the name of your organization.)
Build the image:
Run the container with the following:
You should see the following output:
You can also run the CLI application with an argument:
If you require additional packages that can be installed with the pip
package manager, we recommend using a multistage build. This process involves installing packages in a virtual environment using the latest-dev
variant, then copying this environment over to the minimal runtime image. The following example uses a multi-stage build to install packages necessary to run a Flask web application.
First, create a project folder for the example:
Next, create the script for our Flask web application:
Next, create a requirements.txt
file listing dependencies:
Finally, let's create a Dockerfile for our image build. (Make sure to replace the value of the ORGANIZATION environmental variable with the name of your organization.)
Build the image:
Run a container to serve the web application:
The application should now be accessible at http://localhost:8000/.
Chainguard Containers are minimal container images that are secure by default.
In many cases, the Chainguard Containers tagged as :latest
contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev
variant.
Although the -dev
container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev
variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.
To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.
In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.
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" version of this image:
Apache-2.0
BSD-2-Clause
GCC-exception-3.1
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
MPL-2.0
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