Self-host lldap with Levelrail
VerifiedA lightweight LDAP server with a friendly web UI, built for homelab and small-team authentication.
- Authorlldap
- LicenceGPL-3.0-only
- Memory128 MiB
- Archarm64
- Services1
How to self-host lldap
-
Pull the images
One image is pulled on your server.
Show images
lldap/lldap:v0.6.3
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 17170, 3890.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 1 setting is preset, 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.
lldap requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 17170, 3890
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-only, copyleft license
- Verified. Verified on arm64 with image tag v0.6.3. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes ports 17170, 3890 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then lldap. 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 lldap docs page.
Deploy lldap your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy lldap from the CLI
levelrail-cli templates deploy lldap --name my-lldap Deploy lldap with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/lldap/deploy lldap configuration
lldap services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| lldap | lldap/lldap:v0.6.3 | 17170, 3890 | lldap_data -> /data |
lldap environment variables
| Variable | Service | Value |
|---|---|---|
| LLDAP_JWT_SECRET | lldap | Generated at deploy |
| LLDAP_KEY_SEED | lldap | Generated at deploy |
| LLDAP_LDAP_BASE_DN | lldap | Preset by the template |
| LLDAP_LDAP_USER_PASS | lldap | Generated at deploy |
Ports and volumes
- Ports
- 17170, 3890
- Volumes
- 1 named mount: lldap_data -> /data
lldap FAQ
How much memory does lldap need?
The catalog lists about 128 MiB of memory for lldap.
Does lldap run on arm64?
For lldap, arm64 is tested; amd64 is image published.
What licence is lldap under?
lldap is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does lldap need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does lldap use?
lldap listens on ports 17170 and 3890 inside the stack.
Where does lldap keep its data?
In a named volume: lldap_data mounted at /data.
Can I deploy lldap 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 lldap, 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 lldap/lldap:v0.6.3 is what you deploy there.