Skip to content
Documentation Prelude Topology Engine 1.0.0

Air-gapped install

Run Prelude TE on a host that has no Internet access — image transfer, license validation, and registration considerations.

Prelude TE runs perfectly well on an air-gapped host. The only piece that talks to the outside world is the license validator, and it has a documented offline mode.

Transferring the image

The Prelude TE container image is published publicly to registry.arolo-solutions.com/prelude/prelude-te. From a host with Internet access, save the image to a file:

docker pull registry.arolo-solutions.com/prelude/prelude-te:1.0.0
docker save registry.arolo-solutions.com/prelude/prelude-te:1.0.0 \
  -o prelude-te-1.0.0.tar

Transfer prelude-te-1.0.0.tar to the air-gapped host through your usual mechanism (USB drive, sneakernet, internal artifact registry, …), then load it:

docker load -i prelude-te-1.0.0.tar

From there, run the engine the same way you would in a connected deployment — see Docker or Podman.

Licensing in an air-gapped install

The engine validates its license against the Arolo Portal on a regular cadence. In an air-gapped install, that traffic cannot reach the portal, so the engine offers an offline import flow:

  1. Open Profile → Licensing in the web UI.
  2. Click Offline import.
  3. The form generates a request payload signed by the engine's hardware fingerprint.
  4. Move the payload to a connected host, exchange it with the Arolo Portal, and bring back the signed license blob.
  5. Paste the blob into the Offline import form to activate it.

Contact contact@arolo-solutions.com for the exchange procedure if you have not done an air-gapped license exchange before.

Registration

The community registration flow described in Getting Started / Licensing needs Internet access — the engine reaches the Portal directly during registration. On an air-gapped host, use the offline import flow above with a Community license blob instead of running the registration wizard.

NATS and other outputs

Outputs live entirely on your network — they do not need Internet access. Configure your NATS server's address as usual; the engine only ever talks to the address you give it.

Updates

Cycle the image the same way you brought it in: pull on a connected host, docker save, transfer the tar, docker load, and restart the engine. The SQLite database is migrated automatically on first start with the new image. See Upgrade for the version-to-version notes.

Filtering by: