Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 4. Installing Discovery containers with the disconnected installation process
The disconnected installation process is required when you want to run Discovery from a system that does not have internet access, also commonly referred to as a disconnected, offline, or air-gapped environment. During the Discovery disconnected installation process, you must complete some steps on a connected system, one that has internet connectivity. These steps include obtaining the container images from the Red Hat Ecosystem Catalog website and then transferring the images to the disconnected system that you intend to use as the Discovery server. You also complete steps on the disconnected system to install, configure the environment for, and start the Discovery containers.
The disconnected installation process uses Podman to install the containers for the Discovery server. You will need sudo permissions to install Podman on your system. However, you must not run the Discovery server using sudo or as the root user.
Prerequisites
- Before you begin, ensure that all hardware, software, and environment prerequisites are installed and configured. For more information about the prerequisites, see Installing prerequisites for Discovery.
Procedure
To install Discovery with the disconnected installation process, you do the following tasks:
From the connected system, run a series of commands:
- Access and download the container images.
From the disconnected system, run a series of commands:
- Transfer the container images to the disconnected system.
- Install, configure, and start the Discovery server containers.
4.1. Installing the Discovery database and server container images for the disconnected installation
During the disconnected installation of the Discovery server, you begin with a connected system to install the Podman container management tool and obtain the Discovery container images on the Red Hat Ecosystem Catalog website. You then transfer those container images to the disconnected system where you want to run Discovery, install Podman on the disconnected system, configure Discovery, and start the Discovery application.
Prerequisites
- The connected system on which you are downloading the Discovery container images must be connected to the internet.
- The connected system must be able to connect to the Red Hat Ecosystem Catalog.
-
The disconnected system that you are using must be able to install Red Hat standard packages through
dnf.
Procedure
To install the Discovery server with the disconnected installation process, use the following steps:
On the connected system
Log in to the Red Hat Ecosystem Catalog (the registry.redhat.io website). When prompted, supply your Red Hat Customer Portal account credentials.
podman login registry.redhat.io
Pull the Discovery container images and save them into as a
.tar.gzfile.podman pull registry.redhat.io/discovery/discovery-ui-rhel9:1.0 registry.redhat.io/discovery/discovery-server-rhel9:1.10 registry.redhat.io/rhel9/postgresql-15:latest registry.redhat.io/rhel9/redis-6:latest podman save --multi-image-archive registry.redhat.io/discovery/discovery-ui-rhel9:1.0 registry.redhat.io/discovery/discovery-server-rhel9:1.10 registry.redhat.io/rhel9/postgresql-15:latest registry.redhat.io/rhel9/redis-6:latest | gzip > discovery-images.tar.gz
On the disconnected system
-
Use the transfer method of your choice to transfer
discovery-images.tar.gzto the disconnected system where you are going to install Discovery: Load the container images into local storage for Podman.
podman load -i discovery-images.tar.gz
Run the following commands to get the Discovery installer.
sudo subscription-manager repos --enable <repository> sudo dnf install -y discovery-installer
NoteIn the preceding command, replace <repository> with the following values:
-
For Red Hat Enterprise Linux 8, replace <repository> with
discovery-1-for-rhel-8-x86_64-rpms -
For Red Hat Enterprise Linux 9, replace <repository> with
discovery-1-for-rhel-9-x86_64-rpms
-
For Red Hat Enterprise Linux 8, replace <repository> with
Run the following command to run the Discovery installer.
discovery-installer install
NoteWhen you run the
discovery-installer installcommand for the first time, it will prompt you to enter a server password. This is the password you will use to log in to Discovery.Start the Discovery application.
systemctl --user start discovery-app
NoteThe first time that Discovery runs may take a long time to complete. To get a better idea about the status of the product, the following commands can be run to provide more verbose data during the initial run of Discovery.
systemctl --user status discovery-app podman ps -a
journalctl -t discovery-app journalctl -t discovery-server
podman logs --since 1m -f discovery-server
4.2. Changing the Discovery password
You can change the Discovery server password, and it is possible that security standards at your organization might require that you change it. At a minimum, you should change the password value to align with common security best practices.
The server administrator password must be:
- at least ten characters
- cannot be a word found in the dictionary
- cannot be the previously provided Discovery default password
- cannot be numeric only
To reset the administrator password, run the following command and follow the prompts to enter the new password:
discovery-installer create-server-password
Follow the prompts to change and verify the password. If Discovery is running when the password is changed, Discovery must be restarted for the changes to take effect.
To restart Discovery, run the following command:
systemctl --user restart discovery-app
Red Hat does not provide support for lost passwords for Discovery, and Discovery does not offer a method to recover passwords; however, you can reset your password.
4.3. Setting other post-installation preferences
The following steps are optional, but can improve the efficiency and usability of your Discovery application.
To remain logged in to Discovery, use the following command:
loginctl enable-linger $USER
- If you want to access Discovery on another computer in the same network, you must allow traffic on TCP port 9443 through any firewall to or on the system that is running the Discovery server.
