haproxy + ucarp

This image runs a haproxy + nginx for SSL termination with ucarp to make it highly available.

This image uses host networking, which requires Docker >= 0.11. For a pipework based version working with older Docker versions, see the legacy-pipework branch.

Configuration

To configure haproxy, you can either bind-mount a haproxy.cfg from your host system to /haproxy/haproxy.cfg in the container or create a custom image by using a Dockerfile like this:

FROM fish/haproxy-docker
ADD  haproxy.cfg /haproxy/haproxy.cfg

Setup

Start a container like this on two hosts:

$ docker run -e DEV=eth1 --privileged --net host fish/haproxy-docker 10.0.1.201 foobar23 [additional IPs..]

Now you should have two haproxy+nginx running and ucarp running on the given interface, making sure only one listens on 10.0.1.201 (and optionally on additional IPs).

Failure Scenarios

If any service (haproxy or nginx) goes down, the container is supposed to kill UCARP so the IP gets removed and the backup can take over.

If for any reasons this isn't working, kill the container manually. This should cause the backup to take over.

If this is not the case, there is a problem with the backup container. You might want to restart it.