phoenixadb/glpi repository overview

⁠Quick reference

Maintained by: Arnaud DE BOCK Twitter⁠, LinkedIn⁠

• Supported architectures: arm64v8

⁠What is GLPI?

GLPI is a free (as in “free speech” not as in “free beer”!) asset and helpdesk management solution accessible from a web browser built to manage all you asset management issues, from hardware components and software inventories management to user helpdesk management. (source: https://glpi-install.readthedocs.io/en/latest/index.html⁠)

⁠How to use this image

$ docker run --name some-glpi --network some-network -d phoenixadb/glpi

The following environment variables are also honored for configuring your GLPI instance:

• -e TIMEZONE=...
• -e GLPI_DB_HOST=...
• -e GLPI_DB_NAME=...
• -e GLPI_DB_USER=...
• -e GLPI_DB_PASSWORD=...

If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:

$ docker run --name some-glpi -p 8080:80 -d glpi Then, access it via http://localhost:8080⁠ or http://host-ip:8080⁠ in a browser.

If you'd like to use an external database instead of a mysql container, specify the hostname and port with GLPI_DB_HOST along with the password in GLPI_DB_PASSWORD and the username in GLPI_DB_USER (if it is something other than root):

$ docker run --name some-glpi -e GLPI_DB_HOST=10.1.2.3:3306 \
    -e GLPI_DB_USER=... -e GLPI_DB_PASSWORD=... -d glpi

⁠Docker Secrets

As an alternative to passing sensitive information via environment variables, _FILE may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in /run/secrets/<secret_name> files. For example:

$ docker run --name some-glpi -e GLPI_DB_PASSWORD_FILE=/run/secrets/mysql-root ... -d phoenixadb/glpi:tag Currently, this is supported for GLPI_DB_HOST, GLPI_DB_USER, GLPI_DB_PASSWORD, GLPI_DB_NAME.

... via docker stack deploy or docker-compose Example stack.yml for GLPI:

version: '3.1'

services:

  glpi:
    image: phoenixadb/glpi:latest
    restart: always
    ports:
      - 8080:80
    environment:
      GLPI_DB_HOST: db
      GLPI_DB_USER: exampleuser
      GLPI_DB_PASSWORD: examplepass
      GLPI_DB_NAME: exampledb
    volumes:
      - glpi:/var/www/html

  db:
    image: mysql:5.7
    restart: always
    environment:
      MYSQL_DATABASE: exampledb
      MYSQL_USER: exampleuser
      MYSQL_PASSWORD: examplepass
      MYSQL_RANDOM_ROOT_PASSWORD: '1'
    volumes:
      - db:/var/lib/mysql

volumes:
  glpi:
  db:

Try in PWD

Run docker stack deploy -c stack.yml glpi (or docker-compose -f stack.yml up), wait for it to initialize completely, and visit http://swarm-ip:8080, http://localhost:8080, or http://host-ip:8080 (as appropriate).

⁠Adding additional libraries / extensions

This image does not provide any additional PHP extensions or other libraries, even if they are required by popular plugins. There are an infinite number of possible plugins, and they potentially require any extension PHP supports. Including every PHP extension that exists would dramatically increase the image size.

If you need additional PHP extensions, you'll need to create your own image FROM this one.

⁠Include pre-installed themes / plugins

Mount the volume containing your plugins to the proper directory; and then apply follow the procedure from GLPI. Ensure read/write/execute permissions are in place for the user.

Plugins go in a subdirectory in /var/www/html/plugins/

⁠Accounts

You have 4 different example of accounts provided by default

• glpi/glpi for super-admin
• tech/tech for technicians
• postonly/postonly only for helpdesk
• normal/normal for users

Do not forget to remove them after installing GLPI.