• 1.4.27, 1.4 (1.4/Dockerfile)
• 1.4.27-alpine, 1.4-alpine (1.4/alpine/Dockerfile)
• 1.5.18, 1.5 (1.5/Dockerfile)
• 1.5.18-alpine, 1.5-alpine (1.5/alpine/Dockerfile)
• 1.6.5, 1.6, 1, latest (1.6/Dockerfile)
• 1.6.5-alpine, 1.6-alpine, 1-alpine, alpine (1.6/alpine/Dockerfile)

For more information about this image and its history, please see the relevant manifest file (library/haproxy). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the haproxy/tag-details.md file in the docker-library/docs GitHub repo.

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).

wikipedia.org/wiki/HAProxy

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.5
COPY haproxy.cfg /usr/local/etc/haproxy/haproxy.cfg

$ docker build -t my-haproxy .

$ docker run -it --rm --name haproxy-syntax-check haproxy:1.5 haproxy -c -f /usr/local/etc/haproxy/haproxy.cfg

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

$ docker run -d --name my-running-haproxy -v /path/to/haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg:ro haproxy:1.5

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.

This image is officially supported on Docker version 1.11.2.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

Documentation for this image is stored in the haproxy/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.