armel organization is deprecated in favor of the more-specific
arm32v5 organization, as per https://github.com/docker-library/official-images#architectures-other-than-amd64. Please adjust your usages accordingly.
Supported tags and respective
THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289 IS STILL IN-PROGRESS (which is the first step towards proper multiarch images)
PLEASE DO NOT USE THEM FOR IMPORTANT THINGS
This image is built from the source of the official image of the same name (
haproxy). Please see that image's description for links to the relevant
If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the
tianon/jenkins-groovy GitHub repository, which are responsible for creating the Jenkins jobs which build them.
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is HAProxy?
HAProxy is a free, open source high availability solution, providing load balancing and proxying for TCP and HTTP-based applications by spreading requests across multiple servers. It is written in C and has a reputation for being fast and efficient (in terms of processor and memory usage).
How to use this image
Since no two users of HAProxy are likely to configure it exactly alike, 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.
It is also worth checking out the
examples/ directory from upstream.
Note: Many configuration examples propose to put
daemon into the
global section to run haproxy as daemon. Do not configure this or the Docker container will exit immediately after launching because the haproxy process would go into the background.
FROM haproxy:1.7 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 --name haproxy-syntax-check my-haproxy haproxy -c -f /usr/local/etc/haproxy/haproxy.cfg
Run the container
$ docker run -d --name my-running-haproxy my-haproxy
You may 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. Make sure the port you're using is free.
Directly via bind mount
$ docker run -d --name my-running-haproxy -v /path/to/etc/haproxy:/usr/local/etc/haproxy:ro haproxy:1.7
Note that your host's
/path/to/etc/haproxy folder should be populated with a file named
haproxy.cfg. If this configuration file refers to any other files within that folder then you should ensure that they also exist (e.g. template files such as
404.http, and so forth). However, many minimal configurations do not require any supporting files.
If you used a bind mount for the config and have edited your
haproxy.cfg file, you can use haproxy's graceful reload feature by sending a
SIGHUP to the container:
$ docker kill -s HUP my-running-haproxy
The entrypoint script in the image checks for running the command
haproxy and replaces it with
haproxy-systemd-wrapper from haproxy upstream which takes care of signal handling to do the graceful reload. Under the hood this uses the
-sf option of haproxy so "there are two small windows of a few milliseconds each where it is possible that a few connection failures will be noticed during high loads" (see Stopping and restarting HAProxy).
View license information for the software contained in this image.