Supported tags and respective Dockerfile links

• 2.2.4, 2.2, latest
• 2.1.9, 2.1
• 2.0.18, 2.0
• 1.9.16, 1.9
• 1.8.26, 1.8
• 1.7.12, 1.7
• 1.6.15, 1.6
• 1.5.19, 1.5

Quick reference

• Where to get help:
  HAProxy mailing list, HAProxy Community Slack or #haproxy on FreeNode

• Where to file issues:
  https://github.com/haproxytech/haproxy-docker-arm32v7/issues

• Maintained by:
  HAProxy Technologies

• Supported architectures: (more info)
  amd64

• Image updates:
  commits to haproxytech/haproxy-docker-arm32v7, top level haproxytech/haproxy-docker-arm32v7 image folder

• Source of this description:
  README.md

What is HAProxy?

HAProxy is the fastest and most widely used open-source load balancer and application delivery controller. Written in C, it has a reputation for efficient use of both processor and memory. It can proxy at either layer 4 (TCP) or layer 7 (HTTP) and has additional features for inspecting, routing and modifying HTTP messages.

It comes bundled with a web UI, called the HAProxy Stats page, that you can use to monitor error rates, the volume of traffic and latency. Features can be toggled on by updating a single configuration file, which provides a syntax for defining routing rules, rate limiting, access controls, and more.

Other features include:

• SSL/TLS termination
• Gzip compression
• Health checking
• HTTP/2
• gRPC support
• Lua scripting
• DNS service discovery
• Automatic retries of failed conenctions
• Verbose logging

How to use this image

This image is being shipped with a trivial sample configuration and for any real life use it should be configured according to the extensive documentation and examples. We will now show how to override shipped haproxy.cfg with one of your own.

Create a Dockerfile

FROM haproxytech/haproxy-arm32v7:2.0
COPY haproxy.cfg /usr/local/etc/haproxy/haproxy.cfg

Build the container

$ docker build -t my-haproxy .

Test the configuration file

$ docker run -it --rm my-haproxy haproxy -c -f /usr/local/etc/haproxy/haproxy.cfg

Run the container

$ docker run -d --name my-running-haproxy my-haproxy

You will also need to publish the ports your HAProxy is listening on to the host by specifying the -p option, for example -p 8080:80 to publish port 8080 from the container host to port 80 in the container.

Directly via bind mount

$ docker run -d --name my-running-haproxy -v /path/to/etc/haproxy:/usr/local/etc/haproxy:ro haproxytech/haproxy-arm32v7:2.0

Note that your host's /path/to/etc/haproxy folder should be populated with a file named haproxy.cfg as well as any other accompanying files local to /etc/haproxy.

Reloading config

To be able to reload HAProxy configuration, you can send SIGHUP to the container:

$ docker kill -s HUP my-running-haproxy

To achieve seamless reloads it is required to use expose-fd listeners and socket transfers which are not enabled by default. More on this topic is in the blog post Truly Seamless Reloads with HAProxy.

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).