This image will be deprecated soon. Please use dockercloud/haproxy instead: https://github.com/docker/dockercloud-haproxy
https://hub.docker.com/r/dockercloud/haproxy/
HAProxy image that balances between linked containers and, if launched in Tutum, reconfigures itself when a linked cluster member redeploys, joins or leaves
tutum/haproxy:latest github branch master
tutum/haproxy:0.2.x github tag 0.2.x
tutum/haproxy:0.1 github tag 0.1
Note: the following configuration is for 0.2.x, which is not compatible with version 0.1.
Launch your application container that exposes port 80:
docker run -d --name web1 tutum/hello-world
docker run -d --name web2 tutum/hello-world
Then, run tutum/haproxy linking it to the target containers:
docker run -d -p 80:80 --link web1:web1 --link web2:web2 tutum/haproxy
The tutum/haproxy container will listen in port 80 and forward requests to both web1 and web2 backends using a roundrobin algorithm.
*container: the building block of docker. *service: the building block of tutum and tutum/haproxy
What is a service? Service is a set of containers that have the same functionality. Usually, containers are created with the same parameters can be considered as a service. Service is a perfect concept for the load balancing management. When you scale up/down a service (changing the number of containers in the service), haproxy will balance the load accordingly.
To set containers in one service, you can:
- Run
tutum/haproxywith Tutum: When you set a link in Tutum, it sets a link between services, everything is done transparently. - Run
tutum/haproxyoutside tutum: When you link containers totutum/haproxy, the link alias matters. Any link alias sharing the same prefix and followed by "-/_" with an integer is considered from the same service. For example:web-1andweb-2belong to serviceweb,app_1andapp_2are from serviceapp, butapp1andweb2are from different services.
###Global and default settings of HAProxy###
Settings in this part is immutable, you have to redeploy HAProxy service to make the changes take effects
| env var | default | description |
|---|---|---|
| DEFAULT_SSL_CERT | Default ssl cert, a pem file content with private key followed by public certificate, '\n'(two chars) as the line separator. should be formatted as one line - see SSL Termination | |
| EXTRA_SSL_CERTS | List of extra certificate names separated by space, eg. CERT1 CERT2 CERT3. You also need to specify each certifcate as separate env variables like so: CERT1="<cert-body1>", CERT2="<cert-body2>", CERT3="<cert-body3>" |
|
| BALANCE | roundrobin | load balancing algorithm to use. Possible values include: roundrobin, static-rr, source, leastconn. See:HAProxy:balance |
| MODE | http | mode of load balancing for HAProxy. Possible values include: http, tcp, health |
| MAXCONN | 4096 | sets the maximum per-process number of concurrent connections. |
| OPTION | redispatch | comma-separated list of HAProxy option entries to the default section. |
| RSYSLOG_DESTINATION | 127.0.0.1 | the rsyslog destination to where HAProxy logs are sent |
| SSL_BIND_OPTIONS | no-sslv3 | explicitly set which SSL bind options will be used for the SSL server. This sets the HAProxy ssl-default-bind-options configuration setting. The default will allow only TLSv1.0+ to be used on the SSL server. |
| SSL_BIND_CIPHERS | explicitly set which SSL ciphers will be used for the SSL server. This sets the HAProxy ssl-default-bind-ciphers configuration setting. |
|
| STATS_PORT | 1936 | port for the HAProxy stats section. If this port is published, stats can be accessed at http://<host-ip>:<STATS_PORT>/ |
| STATS_AUTH | stats:stats | username and password required to access the Haproxy stats. |
| TIMEOUT | connect 5000, client 50000, server 50000 | comma-separated list of HAProxy timeout entries to the default section. |
| HEALTH_CHECK | check | set health check on each backend route, possible value: "check inter 2000 rise 2 fall 3". See:HAProxy:check |
| EXTRA_GLOBAL_SETTINGS | comma-separated string of extra settings, and each part will be appended to GLOBAL section in the configuration file. To escape comma, use \,. Possible value: tune.ssl.cachesize 20000, tune.ssl.default-dh-param 2048 |
|
| EXTRA_DEFAULT_SETTINGS | comma-separated string of extra settings, and each part will be appended to DEFAULT section in the configuration file. To escape comma, use \, |
|
| EXTRA_BIND_SETTINGS | comma-separated string(:) of extra settings, and each part will be appended to the related port bind section in the configuration file. To escape comma, use \,. Possible vaule: 443:accept-proxy, 80:name http |
|
| HTTP_BASIC_AUTH | a comma-separated list of credentials(<user>:<pass>) for HTTP basic auth, which applies to all the backend routes. To escape comma, use \,. Attention: DO NOT rely on this for authentication in production |
|
| CA_CERT | CA cert for haproxy to verify the client. Use the same format as DEFAULT_SSL_CERT |
|
| MONITOR_PORT | the port number where monitor_uri should be added to. Use together with MONTIOR_URI. Possible value: 80 |
|
| MONITOR_URI | the exact URI which we want to intercept to return HAProxy's health status instead of forwarding the request.See: http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4-monitor-uri. Possible value: /ping |
###Settings in linked application services###
Settings here can overwrite the settings in HAProxy, which are only applied to the linked services. If run in Tutum, when the service redeploys, joins or leaves HAProxy service, HAProxy service will automatically update itself to apply the changes
| env var | description |
|---|---|
| APPSESSION | sticky session option. possible value JSESSIONID len 52 timeout 3h. See:HAProxy:appsession |
| COOKIE | sticky session option. possible value SRV insert indirect nocache. See:HAProxy:cookie |
| SSL_CERT | ssl cert, a pem file with private key followed by public certificate, '\n'(two chars) as the line separator |
| DEFAULT_SSL_CERT | similar to SSL_CERT, but stores the pem file at /certs/cert0.pem as the default ssl certs. If multiple DEFAULT_SSL_CERT are specified in linked services and HAProxy, the behavior is undefined |
| EXCLUDE_PORTS | comma separated port numbers(e.g. 3306, 3307). By default, HAProxy will add all the ports exposed by the application services to the backend routes. You can exclude the ports that you don't want to be routed, like database port |
| TCP_PORTS | comma separated ports(e.g. 9000, 9001, 2222/ssl). The port listed in TCP_PORTS will be load-balanced in TCP mode. Port ends with /ssl indicates that port needs SSL termination. |
| BALANCE | load balancing algorithm to use. Possible values include: roundrobin, static-rr, source, leastconn. See:HAProxy:balance |
| FORCE_SSL | if set(any value) together with ssl termination enabled. HAProxy will redirect HTTP request to HTTPS request. |
| VIRTUAL_HOST | specify virtual host and virtual path. Format: [scheme://]domain[:port][/path], .... wildcard * can be used in domain and path part |
| HEALTH_CHECK | set health check on each backend route, possible value: "check inter 2000 rise 2 fall 3". See:HAProxy:check |
| HTTP_CHECK | enable HTTP protocol to check on the servers health, possible value: "OPTIONS * HTTP/1.1\r\nHost:\ www". See:HAProxy:httpchk |
| VIRTUAL_HOST_WEIGHT | an integer of the weight of an virtual host, used together with VIRTUAL_HOST, default:0. It affects the order of acl rules of the virtual hosts. The higher weight one virtual host has, the more priority that acl rules applies. |
| HSTS_MAX_AGE | enable HSTS. It is an integer representing the max age of HSTS in seconds, possible value: 31536000 |
| GZIP_COMPRESSION_TYPE | enable gzip compression. The value of this envvar is a list of MIME types that will be compressed, possible value: text/html text/plain text/css |
| OPTION | comma-separated list of HAProxy option entries. option specified here will be added to related backend or listen part, and overwrite the OPTION settings in the HAProxy container |
| EXTRA_SETTINGS | comma-separated string of extra settings, and each part will be appended to either related backend section or listen session in the configuration file. To escape comma, use \,. Possible value: balance source |
Check the HAProxy configuration manual for more information on the above.
Both virtual host and virtual path can be specified in environment variable VIRTUAL_HOST, which is a set of comma separated urls with the format of [scheme://]domain[:port][/path].
| item | default | description |
|---|---|---|
| scheme | http | possible values: http, https, wss |
| domain | virtual host. * can be used as the wildcard |
|
| port | 80/443 | port number of the virtual host. When the scheme is https wss, the default port will be to 443 |
| /path | virtual path, starts with /. * can be used as the wildcard |
###examples of matching
| virtual host | match | not match |
|---|---|---|
| http://example.com | example.com | www.example.com |
| example.com | example.com | www.example.com |
| example.com:90 | example.com:90 | example.com |
| https://example.com | https://example.com | example.com |
| https://example.com:444 | https://example.com:444 | https://example.com |
| *.example.com | www.example.com | example.com |
| *example.com | www.example.com, example.com, anotherexample.com | www.abc.com |
| www.e\*e.com | www.example.com, www.exxe.com | www.axxa.com |
| www.example.\* | www.example.com, www.example.org | example.com |
| * | any website with HTTP | |
| https://* | any website with HTTPS | |
| */path | example.com/path, example.org/path?u=user | example.com/path/ |
| */path/ | example.com/path/, example.org/path/?u=user | example.com/path, example.com/path/abc |
| */path/* | example.com/path/, example.org/path/abc | example.com/abc/path/ |
| */*/path/* | example.com/path/, example.org/abc/path/, example.net/abc/path/123 | example.com/path |
| */*.js | example.com/abc.js, example.org/path/abc.js | example.com/abc.css |
| */*.do/ | example.com/abc.do/, example.org/path/abc.do/ | example.com/abc.do |
| */path/*.php | example.com/path/abc.php | example/abc.php, example.com/root/abc.php |
| *.example.com/*.jpg | www.example.com/abc.jpg, abc.exampe.com/123.jpg | example.com/abc.jpg |
| */path, */path/ | example.com/path, example.org/path/ | |
| example.com:90, https://example.com | example.com:90, https://example.com |
Note: The sequence of the acl rules generated based on VIRTUAL_HOST are randomly. In HAProxy, when an acl rule with a wide scope(e.g. *.example.com) is put before a rule with narrow scope(e.g. web.example.com), the narrow rule will never be reached. As a result, if the virtual hosts you set have overlapping scopes, you need to use VIRTUAL_HOST_WEIGHT to manually set the order of acl rules, namely, giving the narrow virtual host a higher weight than the wide one.
tutum/haproxy supports ssl termination on multiple certificates. For each application that you want ssl terminates, simply set SSL_CERT and VIRTUAL_HOST. HAProxy, then, reads the certificate from the link environment and sets the ssl termination up.
Attention: there was a bug that if an environment variable value contains "=", which is common in the SSL_CERT, docker skips that environment variable. As a result, multiple ssl termination only works on docker 1.7.0 or higher, or in Tutum.
SSL termination is enabled when:
- at least one SSL certificate is set, and
- either
VIRTUAL_HOSTis not set, or it is set with "https" as the scheme.
To set SSL certificate, you can either:
- set
DEFAULT_SSL_CERTintutum/haprox, or - set
SSL_CERTand/orDEFAULT_SSL_CERTin the application services linked to HAProxy
The difference between SSL_CERT and DEFAULT_SSL_CERT is that, the multiple certificates specified by SSL_CERT are stores in as cert1.pem, cert2.pem, ..., whereas the one specified by DEFAULT_SSL_CERT is always stored as cert0.pem. In that case, HAProxy will use cert0.pem as the default certificate when there is no SNI match. However, when multiple DEFAULT_SSL_CERTICATE is provided, only one of the certificates can be stored as cert0.pem, others are discarded.
The certificate specified in tutum/haproxy or in the linked application services is a pem file, containing a private key followed by a public certificate(private key must be put before the public certificate and any extra Authority certificates, order matters). You can run the following script to generate a self-signed certificate:
openssl req -x509 -newkey rsa:2048 -keyout key.pem -out ca.pem -days 1080 -nodes -subj '/CN=*/O=My Company Name LTD./C=US'
cp key.pem cert.pem
cat ca.pem >> cert.pem
Once you have the pem file, you can run this command to convert the file correctly to one line:
awk 1 ORS='\\n' cert.pem
Copy the output and set it as the value of SSL_CERT or DEFAULT_SSL_CERT.
There are three method to setup affinity and sticky session:
- set
BALANCE=sourcein your application service. When settingsourcemethod of balance, HAProxy will hash the client IP address and make sure that the same IP always goes to the same server. - set
APPSESSION=<value>. use application session to determine which server a client should connect to. Possible value of<value>could beJSESSIONID len 52 timeout 3h - set
COOKIE=<value>. use application cookie to determine which server a client should connect to. Possible value of<value>could beSRV insert indirect nocache
Check HAProxy:appsession and HAProxy:cookie for more information.
By default, tutum/haproxy runs in http mode. If you want a linked service to run in a tcp mode, you can specify the environment variable TCP_PORTS, which is a comma separated ports(e.g. 9000, 9001).
For example, if you run:
docker --name app-1 --expose 9000 --expose 9001 -e TCP_PORTS="9000, 9001" your_app
docker --name app-2 --expose 9000 --expose 9001 -e TCP_PORTS="9000, 9001" your_app
docker run --link app-1:app-1 --link app-2:app-2 -p 9000:9000, 9001:9001 tutum/haproxy
Then, haproxy balances the load between app-1 and app-2 in both port 9000 and 9001 respectively.
Moreover, If you have more exposed ports than TCP_PORTS, the rest of the ports will be balancing using http mode.
For example, if you run:
docker --name app-1 --expose 80 --expose 22 -e TCP_PORTS=22 your_app
docker --name app-2 --expose 80 --expose 22 -e TCP_PORTS=22 your_app
docker run --link app-1:app-2 --link app-2:app-2 -p 80:80 -p 22:22 tutum/haproxy
Then, haproxy balances in http mode at port 80 and balances in tcp on port at port 22.
In this way, you can do the load balancing both in tcp and in http at the same time.
In TCP_PORTS, if you set port that ends with '/ssl', for example 2222/ssl, HAProxy will set ssl termination on port 2222.
Note:
- You are able to set
VIRTUAL_HOSTandTCP_PORTSat the same them, giving more control onhttpmode. - Be careful that, the load balancing on
tcpport is applied to all the services. If you link two(or more) different services using the sameTCP_PORTS,tutum/haproxyconsiders them coming from the same service.
There are two ways to enable the support of websocket:
- As websocket starts using HTTP protocol, you can use virtual host to specify the scheme using
wsorwss. For example, `-e VIRTUAL_HOST="ws://ws.example.com, wss://wss.example.com" - Websocket itself is a TCP connection, you can also try the TCP load balancing mentioned in the previous section.
Launch the service you want to load-balance using Tutum.
Then, launch the load balancer. To do this, select "Jumpstarts", "Proxies" and select tutum/haproxy. During the "Environment variables" step of the wizard, link to the service created earlier (the name of the link is not important), and add "Full Access" API role (this will allow HAProxy to be updated dynamically by querying Tutum's API). If you are using tutumcli, or stackfile, please set role to global
That's it - the proxy container will start querying Tutum's API for an updated list of containers in the service and reconfigure itself automatically, including:
- start/stop/terminate containers in the linked application services
- start/stop/terminate/scale up/scale down/redeploy the linked application services
- add new links to HAProxy
- remove old links from HAProxy
Use the following:
docker run -d --expose 80 --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 80:80 tutum/haproxy
My webapp container exposes port 80 and database ports 8083/8086, and I want the proxy to listen in port 80 without my database ports added to haproxy
docker run -d -e EXCLUDE_PORTS=8803,8806 --expose 80 --expose 8033 --expose 8086 --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 80:80 tutum/haproxy
My webapp container exposes port 8080(or any other port), and I want the proxy to listen in port 8080
Use the following:
docker run -d --expose 8080 --name webapp your_app
docker run -d --link webapp:webapp -p 8080:80 tutum/haproxy
#### I want the proxy to terminate SSL connections and forward plain HTTP requests to my webapp to port 8080(or any port)
Use the following:
docker run -d -e SSL_CERT="YOUR_CERT_TEXT" --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 443:443 -p 80:80 tutum/haproxy
or
docker run -d --link webapp:webapp -p 443:443 -p 80:80 -e DEFAULT_SSL_CERT="YOUR_CERT_TEXT" tutum/haproxy
The certificate in YOUR_CERT_TEXT is a combination of private key followed by public certificate. Remember to put \n between each line of the certificate. A way to do this, assuming that your certificate is stored in ~/cert.pem, is running the following:
docker run -d --link webapp:webapp -p 443:443 -p 80:80 -e DEFAULT_SSL_CERT="$(awk 1 ORS='\\n' ~/cert.pem)" tutum/haproxy
Use the following:
docker run -d -e FORCE_SSL=yes -e SSL_CERT="YOUR_CERT_TEXT" --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 80:80 -p 443:443 tutum/haproxy
Virtual hosts can be configured by the proxy reading linked container environment variables (VIRTUAL_HOST). Here is an example:
docker run -d -e VIRTUAL_HOST="www.webapp1.com, www.webapp1.org" --name webapp1 tutum/hello-world
docker run -d -e VIRTUAL_HOST=www.webapp2.com --name webapp2 your/webapp2
docker run -d --link webapp1:webapp1 --link webapp2:webapp2 -p 80:80 tutum/haproxy
In the example above, when you access http://www.webapp1.com or http://www.webapp1.org, it will show the service running in container webapp1, and http://www.webapp2.com will go to container webapp2.
If you use the following:
docker run -d -e VIRTUAL_HOST=www.webapp1.com --name webapp1 tutum/hello-world
docker run -d -e VIRTUAL_HOST=www.webapp2.com --name webapp2-1 tutum/hello-world
docker run -d -e VIRTUAL_HOST=www.webapp2.com --name webapp2-2 tutum/hello-world
docker run -d --link webapp1:webapp1 --link webapp2-1:webapp2-1 --link webapp2-2:webapp2-2 -p 80:80 tutum/haproxy
When you access http://www.webapp1.com, it will show the service running in container webapp1, and http://www.webapp2.com will go to both containers webapp2-1 and webapp2-2 using round robin (or whatever is configured in BALANCE).
docker run -d -e VIRTUAL_HOST="*.node.io" --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 80:80 tutum/haproxy
docker run -d -e VIRTUAL_HOST="web.example.com" -e VIRTUAL_HOST_WEIGHT=1 --name webapp tutum/hello-world
docker run -d -e VIRTUAL_HOST="*.example.com" -e VIRTUAL_HOST_WEIGHT=0 --name app tutum/hello-world
docker run -d --link webapp:webapp --link app:app -p 80:80 tutum/haproxy
docker run -d -e VIRTUAL_HOST="*/path, */path/*" --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 80:80 tutum/haproxy
docker run -d -e VIRTUAL_HOST="*/*.htm, */*.html" --name webapp tutum/hello-world
docker run -d --link webapp:webapp -p 80:80 tutum/haproxy
docker run -d --link webapp:webapp -e STATS_AUTH="auth:auth" -e STATS_PORT=1936 -p 80:80 -p 1936:1936 tutum/haproxy
Replace <subdomain> and <port> with your the values matching your papertrailapp account:
docker run -d --name web1 tutum/hello-world
docker run -d --name web2 tutum/hello-world
docker run -it --env RSYSLOG_DESTINATION='<subdomain>.papertrailapp.com:<port>' -p 80:80 --link web1:web1 --link web2:web2 tutum/haproxy
Within Tutum:
|---- container_a1
|----- service_a ----- |---- container_a2
| (virtual host a) |---- container_a3
internet --- tutum/haproxy--- |
| |---- container_b1
|----- service_b ----- |---- container_b2
(virtual host b) |---- container_b3
Outside Tutum (any Docker server):
|---- container_a1 (virtual host a) ---|
|---- container_a2 (virtual host a) ---|---logic service_a
|---- container_a3 (virtual host a) ---|
internet --- tutum/haproxy--- |
|---- container_b1 (virtual host b) ---|
|---- container_b2 (virtual host b) ---|---logic service_b
|---- container_b3 (virtual host b) ---|
In most cases, tutum/haproxy will configure itself automatically when the linked services change, you don't need to reload it manually. But for some reason, if you have to do so, here is how:
docker exec <haproxy_id> /reload.sh, if you are on the node where tutum/haproxy deploystutum exec <haproxy_uuid> /reload.sh, if you use tutum cli
Note: when reload.sh is invoked, it doesn't necessarily mean that HAProxy will be restarted. In fact, tutum/haproxy will try to get the current information of the the service and calculate a new configuration. HAProxy will only be restarted when the newly generated configuration differs from the current one.