Skip to content

Offline installation (experimental)

Use the offline installer when the installation target cannot access the Irisity Docker registry or the internet. Run it on the same machine where the software will be installed. The bundle contains the installer and application dependencies. Operating-system packages, Docker, NVIDIA drivers, and the NVIDIA Container Toolkit must be installed separately.

Offline installer bundle required

You will need the installer_r33.tar bundle to proceed with offline installation. Contact technicalsupport@irisity.com to obtain the bundle, then transfer it to the installation target using your approved offline transfer method before continuing.

The target must already have the operating-system dependencies. If the target is isolated, obtain these packages and their dependencies from an approved internal repository or offline package media before disconnecting it. For a deployment with separate core and indexer nodes, transfer and run the bundle on each node separately.

Docker credentials are not required

The offline installer loads the bundled images locally. Do not run docker login, and Docker registry credentials are not requested during installation.

Prerequisites

Complete the shared prerequisites on every target node before proceeding.

Verify SSH access back to this machine. This example uses the current account; use the deployment account instead if it is different:

ssh "$USER@127.0.0.1" true

Installation

Have the shared deployment information ready. Use 127.0.0.1 as the SSH address for this local installation.

1. Extract the offline installer bundle

Extract the bundle onto the installation target. Allow enough free space for both the extracted bundle and the installed software.

The example below uses your home directory. Use a directory on a larger data volume if necessary.

mkdir -p ~/irisity-offline-installer && \
tar -xf /path/to/installer_r33.tar -C ~/irisity-offline-installer && \
cd ~/irisity-offline-installer

Keep all extracted files together. The installer is ready to run; no pip installation or additional flags are needed.

2. Initialise the installer

./iris_plus_pro_installer_offline init

Enter 127.0.0.1 as the server address and provide the SSH and deployment configuration for this machine. Docker credentials are not requested in offline mode. If authenticating with an SSH key, load it into your SSH agent before running the installer. When prompted, provide the sudo password, or leave it empty only if the account has passwordless sudo.

3. Run the installer

./iris_plus_pro_installer_offline install

Installation uses the bundled dependencies without downloading Docker images or Python packages. Loading large images and generating models can take time.

Retain the extracted bundle for subsequent offline operations. Use the same Linux account so the installer finds the saved configuration. To install a newer release, follow the System Update steps below.

Values shown in square brackets [] are defaults. Press Enter to accept a default or enter a custom value.

To edit the configuration after installation, use the edit_config command. For example:

source ~/.professional_env/bin/activate && \
iris-plus-pro-installer edit_config && \
deactivate

For additional help

./iris_plus_pro_installer_offline --help

./iris_plus_pro_installer_offline restore --help

HTTPS settings

You can enable HTTPS connectivity during installation. If you need HTTPS connectivity, choose the appropriate value when prompted for the Certificate type variable.

  • In the case of 'official_ca', our reverse proxy will attempt to generate a Let's Encrypt signed certificate.

  • It is required to fill in the domain variable as well.

  • An automatic renew process is included.

  • The domain's A record must be a public IPv4 address that points to your target node.

  • The domain must be publicly accessible due to HTTP-01 validation for certificate generation and automatic renewal process.

  • In the case of 'self_signed', our reverse proxy will attempt to generate a self signed certificate.

  • It is required to fill in the domain variable as well.

  • An automatic renew process is included.

  • You can provide your own certificate and private key pair. Provide the following information when prompted:

    • certificate.crt which represents the certificate.

    • certificate.key which represents the private key.

Once your system is installed, you can proceed to the Licence activation guide to activate your license or follow the Adding Indexers guide to add indexer nodes to your ForensiQ installation.

System Update

1. Obtain the new release bundle

Download the installer_r33.tar bundle for the release you want to install from Irisity and transfer it to the installation target using your approved offline transfer method. Check that the target still meets the prerequisites; any required operating-system package or driver updates must be prepared separately.

2. Extract the new release bundle

Extract the new bundle into a separate directory on the installation target. Allow enough free space for the extracted files. The example below uses your home directory; use a larger data volume if necessary.

mkdir -p ~/irisity-offline-update && \
tar -xf /path/to/installer_r33.tar -C ~/irisity-offline-update && \
cd ~/irisity-offline-update

Keep all extracted files together and run the executable from the new bundle. Use the same Linux account as the original installation so the installer finds the saved configuration.

3. Run the update

./iris_plus_pro_installer_offline update

Follow the on-screen instructions to complete the update. The installer uses the dependencies in the new bundle without downloading Docker images or Python packages; Docker registry credentials are not required. For a deployment with separate core and indexer nodes, transfer the new bundle and repeat these steps on each node separately.

Retain the new extracted bundle for subsequent offline operations.