Self-host osTicket with Levelrail
A widely used open-source support ticket system for teams handling customer requests.
- Memory512 MiB
- Services2
How to self-host osTicket
-
Pull the images
2 images are pulled on your server.
Show images
mariadb:11tiredofit/osticket:1.18.2
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 80.
-
Fill in the secrets
6 secrets are generated and stored encrypted, 6 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.
osTicket requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 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 osTicket. 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 osTicket docs page.
Deploy osTicket your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy osTicket from the CLI
levelrail-cli templates deploy osticket --name my-osticket Deploy osTicket with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/osticket/deploy osTicket configuration
osTicket services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | mariadb:11 | none | osticket_db_data -> /var/lib/mysql |
| osticket | tiredofit/osticket:1.18.2 | 80 | osticket_data -> /www/osticket |
osTicket environment variables
| Variable | Service | Value |
|---|---|---|
| MARIADB_DATABASE | db | Preset by the template |
| MARIADB_PASSWORD | db | Generated at deploy |
| MARIADB_ROOT_PASSWORD | db | Generated at deploy |
| MARIADB_USER | db | Preset by the template |
| ADMIN_EMAIL | osticket | Preset by the template |
| ADMIN_PASS | osticket | Generated at deploy |
| ADMIN_USER | osticket | Generated at deploy |
| DB_HOST | osticket | Preset by the template |
Show all 12 variables
- DB_NAMEosticketPreset by the template
- DB_PASSosticketGenerated at deploy
- DB_USERosticketPreset by the template
- INSTALL_SECRETosticketGenerated at deploy
Ports and volumes
- Ports
- 80
- Volumes
- 2 named mounts: osticket_db_data -> /var/lib/mysql, osticket_data -> /www/osticket
osTicket FAQ
How much memory does osTicket need?
The catalog lists about 512 MiB of memory for osTicket across its 2 services.
Does osTicket run on arm64?
For osTicket, arm64 support is not confirmed; amd64 is unknown.
Does osTicket need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does osTicket bundle?
The template includes MySQL, running as its own service.
Which ports does osTicket use?
osTicket listens on port 80 inside the stack.
Where does osTicket keep its data?
In named volumes: osticket_db_data mounted at /var/lib/mysql and osticket_data mounted at /www/osticket.
Can I deploy osTicket 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 osTicket, 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 mariadb:11, tiredofit/osticket:1.18.2 is what you deploy there.