Image Overview: haproxy

• Overview
• Details
• Tags History
• Provenance

A minimal haproxy base image rebuilt every night from source.

Download this Image

The image is available on cgr.dev:

docker pull cgr.dev/chainguard/haproxy:latest

Usage

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

Please refer to upstream’s excellent (and comprehensive) documentation on the subject of configuring HAProxy for your needs.

Let say you have a haproxy.cfg config file is 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/chainguard/haproxy 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/chainguard/haproxy 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