When you would like to upgrade to the new version of Glpi

It is better to start from the new slate instead of copying the old database volume.

Create a new stack with all the versions taken into account.

mariadb backup using the following method:

The mariadb folder in the host should be provided with the following permissions

sudo chown -R 1001:0 mariadb-master
sudo chown -R 1001:0 mariadb-slave

mariadb-backup --backup --target-dir=/bitnami/mariadb/backup --user=root --password=
# run a prepare command to remove the timestamp requires for INNODB to restore properly
mariadb-backup --prepare --target-dir=/bitnami/mariadb/backup

Restoration:

mariadb-backup --copy-back --target-dir=/bitnami/mariadb/backup

To check and validate if the database is copied properly:

  • connect via phpmyadmin
  • run the following SQL query and check all the rows total are matching with the source.
SELECT 
    table_name AS 'Table Name',
    table_rows AS 'Row Count'
FROM 
    information_schema.tables
WHERE 
    table_schema = 'glpi'
    AND table_type = 'BASE TABLE'
ORDER BY 
    table_rows DESC;

Need to copy the glpicrypt.key file from the old glpi to the new installation

The key file “/var/www/html/glpi/config/glpicrypt.key” used to encrypt/decrypt sensitive data is missing. You should retrieve it from your previous installation or encrypted data will be unreadable.

When you would like to upgrade to the new version of Glpi or new version of Fusion inventory.

For instance if you have installed Glpi 9.5.7 and fusion invnetory 9.5.30 the folder where the data resides is Glpi957fusion9530 image The structure inside the folder is as follows: image

Copy the entire Folder and rename it to the next version ex: glpi957fusion9530 -> glpi958fusion9530 Delete the glpi-frontend ssh into the docker host and change the user group for the Mariadb-master and MariaDB-slave folder as follows

sudo chown -R 1001:1001 mariadb-master
sudo chown -R 1001:1001 mariadb-slave

Make the following changes in the stack code

  mariadb:
    image: 'bitnami/mariadb:latest'
    container_name: mariadb
    hostname: mariadb
    ports:
      - '3306:3306'
    volumes:
      #- /portainer/appdata/glpi957fusion9530/mariadb-master:/bitnami/mariadb
      - /portainer/appdata/glpi958fusion9530/mariadb-master:/bitnami/mariadb
    environment:
      - MARIADB_REPLICATION_MODE=master
      - MARIADB_REPLICATION_USER=
      - MARIADB_REPLICATION_PASSWORD=
      - MARIADB_ROOT_PASSWORD=
      - MARIADB_USER=
      - MARIADB_PASSWORD=
      - MARIADB_DATABASE=
  
  mariadb-slave:
    image: 'bitnami/mariadb:latest'
    container_name: mariadb-slave
    ports:
      - '3307:3306'
    depends_on:
      - mariadb
    volumes:
      #- /portainer/appdata/glpi957fusion9530/mariadb-slave:/bitnami/mariadb
      - /portainer/appdata/glpi958fusion9530/mariadb-slave:/bitnami/mariadb
    environment:
      - MARIADB_REPLICATION_MODE=slave
      - MARIADB_REPLICATION_USER=
      - MARIADB_REPLICATION_PASSWORD=
      - MARIADB_MASTER_HOST=mariadb
      - MARIADB_MASTER_PORT_NUMBER=3306
      - MARIADB_MASTER_ROOT_PASSWORD=
  
  #GLPI Container
  glpi:
    image: diouxx/glpi
    container_name : glpi
    hostname: glpi
    depends_on:
      - mariadb
      - mariadb-slave
    ports:
      - "80:80"
    volumes:
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
      #- /portainer/appdata/glpi957fusion9530/glpi-frontend/var/www/html/glpi/:/var/www/html/glpi
      - /portainer/appdata/glpi958fusion9530/glpi-frontend/var/www/html/glpi/:/var/www/html/glpi
    environment:
      - TIMEZONE=Europe/Paris
      - VERSION_GLPI=9.5.8
    restart: always

Update the stack

Check the mariadb and mariadbslave container is up with no errors

When you launch GLPI choose the upgrade option and point to the glpi database.

  • if glpi page is not served, check the user group /var/www/html/glpi folder changeit as follows. 
    sudo chown -R www-data:www-data /var/www/html
  • If the glpi says the that it couldnt contact the sql server:
    • Using portainer go into Glpi Container and try to Ping MariaDB.
    • make sure the mariadb container is running in the same network of Glpi image
    • Using FileBrowser go to glpi957fusion9530/glpi-frontend/var/www/html/glpi/config/ and edit the config_db.php image

Copy the /var/www/html/glpi/files folder from glpi957fusion9530 -> glpi958fusion9530 (This contains all the PDF files uploaded into the GLPI)

Install fusioninventory plugin

Go to the Duplicati and edit the configuration to backup the newfolder glpi957fusion9530 -> glpi958fusion9530