Chainguard Container for haproxy-fips

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/haproxy-fips: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 HAProxy container image is a minimal image that comes in two variants: a -slim version that only contains the haproxy binary, as well as a regular version that contains a docker-entrypoint.sh script that is compatible with the external docker-library/haproxy image for use with Helm charts or established Docker based deployments.

FIPS Support

The haproxy-fips Chainguard Container ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

Similar to the docker-library/haproxy container image, this image does not come with any default configuration.

Let say you have a haproxy.cfg config file in the current working directory. To test that configuration file, you can run the following command:

docker run -it --rm -v "$(pwd):/etc/haproxy" --name haproxy-syntax-check cgr.dev/ORGANIZATION/haproxy-fips haproxy -c -f /etc/haproxy/haproxy.cfg

In order for the container to work, you need to mount your custom haproxy.cfg file in the container. The following example runs HAProxy with a custom configuration file:

docker run -it --rm -v "$(pwd):/etc/haproxy" cgr.dev/ORGANIZATION/haproxy-fips haproxy -f /etc/haproxy/haproxy.cfg

Helm install

When installing in Kubernetes, securityContexts that drop [ "ALL" ] capabilities interfere with the setcap privileged haproxy. In order to support Kubernetes-based installs which default to dropping ALL capabilities, the necessary modifications must be made to add back NET_ADMIN capabilities.

For example, in the ha-redis chart used by argocd, the values.yaml becomes:

# values.yaml
haproxy:
  enabled: true
  containerSecurityContext:
    capabilities:
      add:
        - NET_BIND_SERVICE

Note on adding users

By default, the Chainguard HAProxy container image runs as the haproxy user and group, with a UID and GID of 65532. You could represent this in an haproxy.cfg file as follows:

global
  user  haproxy
  group haproxy

In the Kubernetes security context, this information might look like this:

securityContext:
  runAsUser: 65532
  runAsGroup: 65532

If you add a user, make sure that you use the correct matching user in your haproxy.cfg file. If the user listed in your haproxy.cfg file doesn't match what's in the Kubernetes security context, it will result in errors.

Documentation and Resources

Please refer to the HAProxy documentation for more information on configuring HAProxy for your needs.

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.