DirectorySecurity AdvisoriesPricing
Sign in
Directory
locust-fips logoFIPS

locust-fips

packaged by Chainguard

Last changed
Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for locust-fips

FIPS-enabled minimal Locust image for distributed load and performance testing of web applications and APIs.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/locust-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Usage

Locust is a load testing tool: you describe user behavior in a locustfile.py and Locust swarms your target system with simulated users, headlessly or through its web UI. This is the FIPS variant, which uses FIPS-validated cryptography.

The image entrypoint is locust, so arguments passed to docker run are passed straight to the locust command.

Example locustfile

Create a file called locustfile.py:

from locust import HttpUser, task, between


class WebsiteUser(HttpUser):
    wait_time = between(1, 5)

    @task
    def load_page(self):
        self.client.get("/")

Running a headless load test

docker run --rm -v $(pwd):/mnt cgr.dev/ORGANIZATION/locust-fips \
  -f /mnt/locustfile.py --headless \
  --users 10 --spawn-rate 2 --run-time 30s \
  --host https://example.com

Running the web UI

Expose Locust's web interface on port 8089 and open it in a browser:

docker run --rm -p 8089:8089 -v $(pwd):/mnt cgr.dev/ORGANIZATION/locust-fips \
  -f /mnt/locustfile.py --host https://example.com

Distributed load testing

Run a master and connect one or more workers over ZeroMQ (port 5557):

# master
docker run --rm -p 8089:8089 -p 5557:5557 -v $(pwd):/mnt cgr.dev/ORGANIZATION/locust-fips \
  -f /mnt/locustfile.py --master

# worker
docker run --rm -v $(pwd):/mnt cgr.dev/ORGANIZATION/locust-fips \
  -f /mnt/locustfile.py --worker --master-host <master-ip>

FIPS

This image links against the FIPS-validated system OpenSSL and cryptography (with openssl-config-fipshardened), so TLS and cryptographic operations — for example the web UI served over HTTPS — run in FIPS mode.

Documentation and resources

  • Locust documentation
  • Writing a locustfile
  • Running distributed
  • GitHub repository

What are Chainguard Containers?

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.

Need additional packages?

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.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Librariescontact us for access.

Trademarks

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.

Licenses

Chainguard's 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

  • BSD-1-Clause

  • BSD-2-Clause

  • BSD-3-Clause

  • BSD-4-Clause-UC

  • CC-PDDC

  • GCC-exception-3.1

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

Chainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.

SLSA compliance at Chainguard

This image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.

PCI DSS at Chainguard

This 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

Related images
locust logo

locust


Category
FIPS
STIG

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.