Skip to content

Before launch#

Make sure that you are the root user before launch!

Before launching the LUNA Index Module, you must perform the following actions:

Distribution unpacking#

The distribution package is an archive lim_v.5.84.0, where v.5.84.0 is a numerical identifier, describing the current LUNA Index Module version.

The archive includes configuration files, required for installation and exploitation. It does not include Docker images for the services. They should be downloaded from the Internet.

Move the distribution package to the directory on your server before the installation. For example, move the files to /root/ directory. The directory should not contain any other distribution or license files except the target ones.

Move the distribution to the /var/lib/luna/ directory.

mv /root/lim_v.5.84.0.zip /var/lib/luna

Install the unzip archiver if it is necessary.

yum install -y unzip

Go to the folder with distribution.

cd /var/lib/luna

Unzip files.

unzip lim_v.5.84.0.zip

Create a symbolic link. The link indicates that the current version of the distribution file is used to run LIM.

ln -s lim_v.5.84.0 lim-current

Create directory to store indexes#

To store indexes and interact with them on the server, you need to create an appropriate directory. This directory will be mounted when the LIM services are launched.

Create folder to store indexes.

mkdir -p /var/lib/luna/lim_storage

Set appropriate permissions to read/write this folder.

chown -R 1001:0 /var/lib/luna/lim_storage

SELinux and Firewall#

You must configure SELinux and Firewall so that they do not block LUNA PLATFORM services.

SELinux and Firewall configurations are not described in this guide.

If SELinux and Firewall are not configured, the installation cannot be performed.

Choose logging method#

There are two methods to output logs in LUNA PLATFORM:

  • Standard log output (stdout).
  • Log output to a file.

Log output settings are set in the settings of each service in the <SERVICE_NAME>_LOGGER section.

If necessary, you can use both methods of displaying logs.

For more information about the LUNA PLATFORM logging system, see the "Logging" section in the administrator manual.

Logging to stdout#

This method is used by default and requires no further action.

Logging to file#

Note: When you enable saving logs to a file, you should remember that logs occupy a certain place in the storage, and the process of logging to a file negatively affects system performance.

To use this method, you need to perform the following additional actions:

  • Before launching the services: Create directories for logs on the server.
  • After launching the services: Activate log recording and set the location of log storage inside LP service containers.
  • During the launch of services: Configure synchronization of log directories in the container with logs on the server using the volume argument at the start of each container.

Synchronization of log directories is already configured in the Docker Compose script, you only need to create directories and activate logging.

See the instructions for enabling logging to files in the "Logging to server" section.

Docker Compose installation#

Note: Docker Compose version 2.24.6 was used when testing this instruction. It is not guaranteed to work with higher versions of Docker Compose.

Download Docker Compose binary:

curl -L "https://github.com/docker/compose/releases/download/v2.24.6/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

Set execution permissions:

chmod +x /usr/local/bin/docker-compose

Create symbolic link:

ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose

Login to registry#

When launching containers, you should specify a link to the image required for the container launching. This image will be downloaded from the VisionLabs registry. Before that, you should login to the registry.

Login and password can be requested from the VisionLabs representative.

Enter login .

After running the command, you will be prompted for a password. Enter password.

In the docker login command, you can enter the login and password at the same time, but this does not guarantee security because the password can be seen in the command history.