Page History
| Table of Contents | ||
|---|---|---|
|
Overview
Starting with version 3.5.0, iDNA Applications runs on a Linux host that you provide. You prepare the host with a supported Linux distribution and Docker; the panagenda installer then sets up iDNA Applications on it as a set of Docker containers. This gives you more flexibility in choosing your virtualization platform and makes it easier to keep the operating system iDNA runs on up to date.
...
- Provide a Linux host that meets the requirements on this page.
- Create and mount the filesystems for iDNA (see Partitioning Running iDNA Applications on Your Own Linux Host).
- Install Docker Engine.
- Download and run the iDNA installer (see Installing iDNA Applications on Linux).
- Log in to iDNA and configure it.
...
- ARM processors (for example AWS Graviton): the iDNA containers exist for x86_64 only.
- Distributions with a read-only system partition, such as Fedora CoreOS, Flatcar or Ubuntu Core: the installer needs to write to
/usr/bin. - Windows , including the and macOS has hosts.
Not supported for production use:
- Windows Subsystem for Linux (WSL2) , and macOS as hostsrunning a supported OS will work, but is not supported for production use.
Note on version RHEL 10: Red Hat Enterprise Linux 10 and most compatible distributions require a processor with the x86-64-v3 feature level (Intel Haswell from 2013 or newer, or a comparable AMD processor). On a virtual machine, the hypervisor must pass these processor features through; an older VMware EVC mode, for example, keeps the operating system from starting. AlmaLinux 10 also offers a build for older processors.
...
- 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:
- Red Hat Enterprise Linux: docs.docker.com/engine/install/rhel
- CentOS Stream: docs.docker.com/engine/install/centos
- Ubuntu: docs.docker.com/engine/install/ubuntu
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; Podman, also with the podman-docker package, is not a substitute for Docker Engine. On Ubuntu, the Docker snap package is not supported.
Afterwards, both of these commands must work:Code Block language bash docker version docker compose version
Docker must start at boot; the iDNA containers start automatically together with Docker:
Code Block language bash 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 enforcing. With a standard Docker installation, the installer needs no changes. Only if Docker itself enforces SELinux on containers does the installer need the package policycoreutils-python-utils, and it asks before it changes anything. On Ubuntu, AppArmor needs no changes.
...
Example for the 300 GB default:
| Filesystem | Recommendation | Size in the example | Why |
|---|---|---|---|
/ (root) | required | 70 GB | The operating system (about 20 GB) and Docker, which keeps the iDNA images and containers in /var/lib/docker. During an upgrade, the old and the new images exist side by side, and the offline installer unpacks about 8 GB in /tmp. Plan the root filesystem generously: a full root filesystem is hard to fix, while the iDNA filesystems are easy to extend. |
/opt/panagenda/appdata | recommended | 30 GB | The Notes database designs iDNA downloads, stored as zipped DXL files. Fills during the first design collection and grows slowly afterwards: about 5 MB per database, 30 to 80 GB in large environments. |
/opt/panagenda/logs | recommended | 5 GB | The log files of all iDNA services. iDNA deletes them after 7 to 14 days; a filesystem of their own keeps an unusual amount of log output away from the operating system and the database. |
/opt/panagenda/pgdata | strongly recommended | 175 GB | The iDNA database, the part that grows continuously. A filesystem of its own keeps a full root or log filesystem from affecting it. |
| unassigned | recommended | 20 GB | Free space in the LVM volume group, to extend a filesystem quickly when needed. |
Rules for the filesystems:
- Use LVM, so that the filesystems can be extended.
- Mount the filesystems before you run the installer, with entries in
/etc/fstab. Otherwise the installer writes into the directories on the root filesystem, and a filesystem mounted there later hides that data. Make Docker wait for the filesystems at boot. If
/opt/panagenda/pgdatais not mounted when Docker starts, the database container finds an empty directory and creates a new, empty database on the root filesystem; iDNA then starts without its data. This setting keeps Docker from starting until the filesystems are mounted (list the filesystems you created):Code Block language bash mkdir -p /etc/systemd/system/docker.service.d cat > /etc/systemd/system/docker.service.d/panagenda-mounts.conf <<'EOF' [Unit] RequiresMountsFor=/opt/panagenda/pgdata /opt/panagenda/appdata /opt/panagenda/logs EOF systemctl daemon-reload
...