aee9645b43
Verified against source code and enhanced with Docusaurus markdown features: Documentation Accuracy Fixes: - Fixed acme.md: Added "letsencrypt" as valid AUTOCONFIG value (was incorrectly shown as "-") - Added reference to ACME docs from environment-variable.md - Verified all features against actual implementation in /src Docusaurus Enhancements Added: - Admonitions (:::note, :::tip, :::warning, :::danger, :::info) for important callouts - Code block titles for all bash/yaml examples (e.g., title="Install EasyHAProxy") - Better structured warnings and notes for limitations - Improved formatting and readability throughout Files Enhanced: - kubernetes.md: Added info boxes, warnings, code titles - docker.md: Added limitation warnings, code titles - swarm.md: Added advantage tips, limitation warnings - acme.md: Fixed Let's Encrypt autoconfig, enhanced requirements with admonitions - ssl.md: Added code block titles for all examples - static.md: Added live reload tip, SSL certificate note - container-labels.md: Added definition explanation, code titles - limitations.md: Restructured with clear warnings and explanations - helm.md: Added warnings, code titles - microk8s.md: Added ingress controller warning, code titles - volumes.md: Added info box about volume purposes - other.md: Added code block titles - environment-variable.md: Added ACME reference note All changes verified against actual Python source code implementation.
2.4 KiB
| sidebar_position |
|---|
| 3 |
Docker
Setup Docker EasyHAProxy
This method involves using a standalone Docker installation to discover containers and configure HAProxy.
EasyHAProxy inspects Docker containers and retrieves labels to configure HAProxy. Once it identifies a container with at least the label 'easyhaproxy.http.host,' it configures HAProxy to redirect traffic to that container. To accomplish this, EasyHAProxy may need to attach the same network to its container.
It's recommended to create a network external to EasyHAProxy, although it's not mandatory.
:::warning Limitations
- You cannot mix Docker containers with Swarm containers.
- This method does not work with containers that use the
--network=hostoption. See limitations for details. :::
For example:
docker network create easyhaproxy
And then run the EasyHAProxy:
docker run -d \
--name easy-haproxy-container \
-v /var/run/docker.sock:/var/run/docker.sock \
-e EASYHAPROXY_DISCOVER="docker" \
# + Environment Variables \
-p 80:80 \
-p 443:443 \
-p 1936:1936 \
--network easyhaproxy
byjg/easy-haproxy
Mapping to /var/run/docker.sock is necessary to discover the docker containers and get the labels;
Running containers
To make your containers "discoverable" by EasyHAProxy, this is the minimum configuration you need:
docker run -d \
--label easyhaproxy.http.host=example.org \
--label easyhaproxy.http.port=80 \
--label easyhaproxy.http.localport=8080 \
--network easyhaproxy
my/image:tag
Once the container is running, EasyHAProxy will detect automatically and start to redirect all traffic from example.org:80 to your container.
You don't need to expose any port in your container.
Please follow the docker label configuration to see other configurations available.
Setup the EasyHAProxy container
You can configure the behavior of the EasyHAProxy by setup specific environment variables. To get a list of the variables, please follow the environment variable guide
Setup certificates with ACME (e.g. Letsencrypt)
Follow this link
Setup your own certificates
Follow this link