glpi/glpi Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

GLPI Docker Images

![Release Build]([***]

!GLPI on docker illustration

GLPI is a free and open source Asset and IT Management Software package, Data center management, ITIL Service Desk, licenses tracking and software auditing.

A few links:

• Report an issue
• Documentation
• Contributing

This repository contains build files for docker images available in Github Container Registry and Docker hub.

How to use this image

via docker compose

docker-compose.yml

yaml
services:
  glpi:
    image: "glpi/glpi:latest"
    restart: "unless-stopped"
    volumes:
      - "./storage/glpi:/var/glpi:rw"
      # For GLPI 10.x, uncomment the following line to create a volume for plugins fetched from the marketplace.
      # - "./storage/glpi_marketplace:/var/www/glpi/marketplace/:rw"
    env_file: .env # Pass environment variables from .env file to the container
    depends_on:
      - db
    ports:
      - "80:80"

  db:
    image: "mysql"
    restart: "unless-stopped"
    volumes:
       - "./storage/mysql:/var/lib/mysql"
    environment:
      MYSQL_RANDOM_ROOT_PASSWORD: "yes"
      MYSQL_DATABASE: ${GLPI_DB_NAME}
      MYSQL_USER: ${GLPI_DB_USER}
      MYSQL_PASSWORD: ${GLPI_DB_PASSWORD}
    expose:
      - "3306"

And an .env file:

.env

env
GLPI_DB_HOST=db
GLPI_DB_PORT=3306
GLPI_DB_NAME=glpi
GLPI_DB_USER=glpi
GLPI_DB_PASSWORD=glpi

Then launch it with:

bash
docker compose up -d

Please note that we setup a random root password for the MySQL database, so you will need to check the logs of the db container to find it:

bash
docker logs <db_container_id>

Once the containers are running, you can access GLPI at http://localhost GLPI will automatically install or update itself if needed.

You can disable this behavior by setting the environment variable GLPI_SKIP_AUTOINSTALL to true in the .env file. Same with GLPI_SKIP_AUTOUPDATE to disable automatic updates.

If so, when accessing the web interface, installation wizard will ask you to provide the database connection details. You can use the following credentials:

• Hostname: db
• Database: glpi
• User: glpi
• Password: glpi

Timezones support

If you want to initialize the timezones support for GLPI, we need to first GRANT the glpi user to access the mysql.time_zone table. So with the docker container running, you can run the following command:

bash
docker exec -it <db_container_id> mysql -u root -p -e "GRANT SELECT ON mysql.time_zone_name TO 'glpi'@'%';FLUSH PRIVILEGES;"

The root password will be the one you found in the logs of the db container previously.

Then you can run the following command to initialize the timezones on the GLPI container:

bash
docker exec -it <glpi_container_id> /var/www/glpi/bin/console database:enable_timezones

Volumes

By default, the glpi/glpi image provides a volume containing its config, marketplace and files directories.

For GLPI 10.0.x version the marketplace directory is not declared in the volume as the path differs. You may want to create a manual volume for the path /var/www/glpi/marketplace if you plan to use it.
If you are building your own GLPI 10.0.x image using the glpi/Dockerfile file, you have to specify the marketplace path using the --build-arg GLPI_MARKETPLACE_DIR=/var/www/glpi/marketplace option.

You can also mount a volume containing your own custom plugins in /var/www/glpi/plugins.

Custom PHP configuration

The following example sets the memory limit to 256M

1. Create an ini file
   custom-config.ini

   ini
   memory_limit = 256M
   

2. Update the volumes configuration

   yaml
   volumes:
     - "./custom-config.ini:/usr/local/etc/php/conf.d/custom-config.ini:ro"
   

3. Apply the changes

   bash
   docker compose up -d
   

4. Check the configuration by running on the GLPI container:

   bash
   docker compose exec glpi sh -c 'php -r "phpinfo();" | grep memory_limit'
   

   Or by browsing the GLPI website under Setup > General > System > Server.

Managing Cron tasks

By default, the image includes a background worker that executes GLPI cron tasks every minute. This behavior is controlled by the GLPI_CRONTAB_ENABLED environment variable.

This is especially useful for horizontal scaling or Kubernetes deployments, where you might want a dedicated container for cron tasks while disabling it on Web or API nodes to avoid automatic tasks duplication.