jmeter

packaged by Chainguard

Chainguard Container for jmeter

Minimal image with Apache JMeter, the Java-based load and performance testing tool for measuring service performance.

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/jmeter:latest

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

Compatibility Notes

Chainguard's jmeter image is comparable to the upstream alpine/jmeter image, with the following differences:

• Like all other Chainguard Containers, jmeter features a stripped-down, minimal design with few-to-zero CVEs.
• The image runs as a non-root user (65532) by default, rather than root.

Getting Started

The image entrypoint sizes the JVM heap from available memory and runs JMeter in non-GUI mode, forwarding any arguments to jmeter.

Run a test plan, writing results to a mounted, writable directory:

docker run --rm -v "$(pwd):/work" -w /work \
  cgr.dev/ORGANIZATION/jmeter:latest \
  -n -t plan.jmx -l results.jtl

Check the version:

docker run --rm cgr.dev/ORGANIZATION/jmeter:latest --version

Running in Kubernetes

JMeter is a CLI load runner, so the idiomatic way to run it on Kubernetes is a Job that executes a non-GUI test plan to completion. Supply the .jmx plan through a ConfigMap and give the container a writable volume for results:

apiVersion: v1
kind: ConfigMap
metadata:
  name: jmeter-plan
data:
  plan.jmx: |
    <!-- your JMeter .jmx test plan -->
---
apiVersion: batch/v1
kind: Job
metadata:
  name: jmeter-load
spec:
  backoffLimit: 0
  template:
    spec:
      restartPolicy: Never
      containers:
        - name: jmeter
          image: cgr.dev/ORGANIZATION/jmeter:latest
          args: ["-n", "-t", "/plan/plan.jmx", "-l", "/tmp/results.jtl"]
          volumeMounts:
            - { name: plan, mountPath: /plan }
            - { name: results, mountPath: /tmp }
      volumes:
        - name: plan
          configMap:
            name: jmeter-plan
        - name: results
          emptyDir: {}

The image runs as non-root, so point -l (and the default jmeter.log) at a writable volume such as the emptyDir mounted at /tmp above. A completed Job pod cannot be exec-ed, so read the run summary from the pod logs:

kubectl logs job/jmeter-load

To retain the raw results or an HTML report (-e -o), mount a PersistentVolumeClaim in place of the emptyDir and write them there.

Documentation and Resources

• Apache JMeter User Manual
• Apache JMeter Best Practices
• Getting Started with JMeter

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:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

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 Libraries — contact 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.