Self-host Semaphore UI with Levelrail
A modern web UI for running Ansible, Terraform, and shell tasks with schedules, history, and access control.
- Authorsemaphoreui
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host Semaphore UI
-
Pull the images
One image is pulled on your server.
Show images
semaphoreui/semaphore:v2.19.14
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 4 settings are 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.
Semaphore UI requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 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 Semaphore UI. 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 Semaphore UI docs page.
Deploy Semaphore UI your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Semaphore UI from the CLI
levelrail-cli templates deploy semaphore --name my-semaphore Deploy Semaphore UI with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/semaphore/deploy Semaphore UI configuration
Semaphore UI services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| semaphore | semaphoreui/semaphore:v2.19.14 | 3000 | semaphore_data -> /var/lib/semaphoresemaphore_config -> /etc/semaphore |
Semaphore UI environment variables
| Variable | Service | Value |
|---|---|---|
| SEMAPHORE_ACCESS_KEY_ENCRYPTION | semaphore | Generated at deploy |
| SEMAPHORE_ADMIN | semaphore | Preset by the template |
| SEMAPHORE_ADMIN_EMAIL | semaphore | Preset by the template |
| SEMAPHORE_ADMIN_NAME | semaphore | Preset by the template |
| SEMAPHORE_ADMIN_PASSWORD | semaphore | Generated at deploy |
| SEMAPHORE_DB_DIALECT | semaphore | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: semaphore_data -> /var/lib/semaphore, semaphore_config -> /etc/semaphore
Semaphore UI FAQ
How much memory does Semaphore UI need?
The catalog lists about 256 MiB of memory for Semaphore UI.
Does Semaphore UI run on arm64?
For Semaphore UI, an arm64 image is published; amd64 is image published.
What licence is Semaphore UI under?
Semaphore UI is licensed under MIT, which is permissive, with few conditions on reuse.
Does Semaphore UI need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Semaphore UI use?
Semaphore UI listens on port 3000 inside the stack.
Where does Semaphore UI keep its data?
In named volumes: semaphore_data mounted at /var/lib/semaphore and semaphore_config mounted at /etc/semaphore.
Can I deploy Semaphore UI 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 Semaphore UI, 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 semaphoreui/semaphore:v2.19.14 is what you deploy there.