Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As of version 3.5.0, panagenda no longer supplies virtual appliance images for VMware or Hyper-V. Existing iDNA appliances keep running and are upgraded with the same installer (see Upgrading iDNA Applications (NEW)).

This page describes what lists the requirements for the Linux host needs. Hand Share it to with the team that provides your Linux servers before the installation, so that the host is ready when , and have them prepare the host before you install iDNA.

The installation at a glance:

...

  1. An x86_64 processor (64-bit Intel or AMD).
  2. A current Docker Engine with the Docker Compose plugin (version 2).
  3. Docker starts at boot. systemd is recommended: the setting that makes Docker wait for the iDNA filesystems is a systemd setting (see Partitioning).
  4. bash and the standard tools the installer checks for (see Access and Software).
  5. Writable directories /opt and /usr/bin.
  6. Ports 80 and 443 free.

panagenda support (support@panagenda.com) helps you install and run iDNA Applications on any distribution that meets these requirements, also on one that including distributions panagenda does not test itself, for example . Examples are Rocky Linux, Oracle Linux, CentOS Stream, Debian or and SUSE Linux Enterprise.

Unsupported Setups

...

  • Root access: the installer runs as root, directly or through sudo.
  • Docker Engine with the Docker Compose plugin (Compose version 2). Install it from Docker's own repository, following Docker's guide for your distribution: Docker does not list AlmaLinux, Rocky Linux and Oracle Linux separately; use the instructions for Red Hat Enterprise Linux or CentOS. Docker's guides first remove Podman and runc, which these distributions may have installed. On Ubuntu, the Docker snap package is not supported.
    Afterwards, both of these commands must work:
    Code Block
    languagebash
    docker version
    docker compose version
    Docker must start at boot; the iDNA containers start automatically together with Docker:
    Code Block
    languagebash
    systemctl enable --now docker
  • Standard tools: tar, grep, awk, sed, hostname, ip, fdisk, one of ss, lsof, netstat or fuser, and timedatectl. A normal server installation includes them; the installer names any that are missing. You also need unzip to unpack the download.
  • SELinux can stay in enforcing mode. With a standard Docker installation, the installer needs no SELinux changes are needed. Only if Docker itself enforces SELinux on containers SELinux support is enabled in Docker ("selinux-enabled": true in /etc/docker/daemon.json) does the installer need the package policycoreutils-python-utils, and it asks before it changes anything. On Ubuntu, AppArmor needs no changes.

...