Self-host GLPI with Levelrail

An IT asset and service management platform with helpdesk ticketing built in.

  • Authorglpi-project
  • LicenceGPL-3.0-or-later
  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host GLPI

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • glpi/glpi:11.0.11
    • mysql:8.4
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 5 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

GLPI requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0-or-later, copyleft 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 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 GLPI. 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 GLPI docs page.

Deploy GLPI your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy GLPI from the CLI

levelrail-cli templates deploy glpi --name my-glpi

Deploy GLPI with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/glpi/deploy

GLPI configuration

GLPI services

ServiceImagePortsVolumes
glpi glpi/glpi:11.0.11 80 glpi_data -> /var/glpi
glpi-db mysql:8.4 none glpi_mysql_data -> /var/lib/mysql

GLPI environment variables

VariableServiceValue
GLPI_DB_HOST glpi Preset by the template
GLPI_DB_NAME glpi Preset by the template
GLPI_DB_PASSWORD glpi Generated at deploy
GLPI_DB_USER glpi Preset by the template
MYSQL_DATABASE glpi-db Preset by the template
MYSQL_PASSWORD glpi-db Generated at deploy
MYSQL_ROOT_PASSWORD glpi-db Generated at deploy
MYSQL_USER glpi-db Preset by the template

Ports and volumes

Ports
80
Volumes
2 named mounts: glpi_data -> /var/glpi, glpi_mysql_data -> /var/lib/mysql

GLPI FAQ

How much memory does GLPI need?

The catalog lists about 512 MiB of memory for GLPI across its 2 services.

Does GLPI run on arm64?

For GLPI, an arm64 image is published; amd64 is image published.

What licence is GLPI under?

GLPI is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.

Does GLPI need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does GLPI bundle?

The template includes MySQL, running as its own service.

Which ports does GLPI use?

GLPI listens on port 80 inside the stack.

Where does GLPI keep its data?

In named volumes: glpi_data mounted at /var/glpi and glpi_mysql_data mounted at /var/lib/mysql.

Can I deploy GLPI on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id glpi for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image glpi/glpi:11.0.11, mysql:8.4 is what you deploy there.

levelrail-cli templates deploy glpi --name my-glpi