Last changed
docker pull cgr.dev/chainguard/haproxy
Need access to a specific tag? Contact us.
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpA minimal haproxy base image rebuilt every night from source.
Chainguard 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.
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.
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:
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:
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:
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:
In the Kubernetes security context, this information might look like this:
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.
Please refer to the HAProxy documentation for more information on configuring HAProxy for your needs.
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" tag of this image:
Apache-2.0
BSD-2-Clause
BSD-3-Clause
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
GPL-3.0-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.