Self-host HAProxy with Levelrail
High-performance TCP and HTTP load balancer on the official image. The install form carries haproxy.cfg as an editable file, so it starts with a working config instead of exiting on a missing one.
- Authorhaproxy
- LicenceGPL-2.0
- Memory64 MiB
- Services1
How to self-host HAProxy
-
Pull the images
One image is pulled on your server.
Show images
haproxy:3.0.5-alpine
-
Create the app
One service starts in a single Compose app, on port 8080.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the address to see the greeting, then edit the config file setting to add your own frontends and backends.
HAProxy requirements
- Memory
- About 64 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-2.0, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then HAProxy. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the HAProxy docs page.
Deploy HAProxy your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy HAProxy from the CLI
levelrail-cli templates install haproxy --name my-haproxy Deploy HAProxy with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/haproxy/install \
-d '{
"name": "my-haproxy"
}' HAProxy configuration
HAProxy services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| haproxy | haproxy:3.0.5-alpine | 8080 | none |
HAProxy environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8080
- Volumes
- none
HAProxy FAQ
How much memory does HAProxy need?
The catalog lists about 64 MiB of memory for HAProxy.
Does HAProxy run on arm64?
For HAProxy, arm64 support is not confirmed; amd64 is unknown.
What licence is HAProxy under?
HAProxy is licensed under GPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does HAProxy need configuration before it starts?
No. The template fills in its own defaults.
Which ports does HAProxy use?
HAProxy listens on port 8080 inside the stack.
Can I deploy HAProxy on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for HAProxy, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image haproxy:3.0.5-alpine is what you deploy there.