Problem:

How to install a dedicated FS to prevent a FS full (error message)

When you execute the first installation command "docker-compose up -d" and if you have this type of error message

ERROR : Named volume « $CORESVC_ROOT_DIR/elastic-data:/usr/share/elasticsearch/data:rw” is used in service “elasticsearch-itopsvision” but no declaration was found in the volumes section.

Solution

In the ".env" file (to be prepared before launching the installation of the Core Services components via the "docker-compose up -d" command), it is now possible to specify the location of the Elastic database and Keycloak data via the CORESVC_ROOT_DIR variable.

The goal is to define a dedicated FS and to be able to control its filling rate

Example:

CORESVC_ROOT_DIR=/appl/CORESERVICES_DATA

ELK_DATA_DIR=${CORESVC_ROOT_DIR}/elastic-data

KEYCLOAK_BASE_DIR=${CORESVC_ROOT_DIR}/keycloak-basedir

Warning: it is imperative in the ELK_DATA_DIR and KEYCLOAK_BASE_DIR variables to specify the CORESVC_ROOT_DIR variable as ${CORESVC_ROOT_DIR} (with braces) and not $CORESVC_ROOT_DIR

Otherwise, you will get an error message like (example for Elastic data):

ERROR : Named volume « $CORESVC_ROOT_DIR/elastic-data:/usr/share/elasticsearch/data:rw” is used in service “elasticsearch-itopsvision” but no declaration was found in the volumes section.

Check the .env file, correct the possible error and run the "docker-compose up -d" command again.

Note: if this CORESVC_ROOT_DIR variable is defined in the file, don't forget to use the "copy-config.sh" script to copy all the config files in the new directories dedicated to the components.