Install bundle contents and offline installation

Prerequisites and authority

Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.

Understand a release bundle

A complete bundle contains the manifest and the files referenced by that manifest, together with installers, deployment configuration and required payloads. A ZIP of repository source is not automatically an offline installer.

Check product name, release version, target OS/architecture, bundle checksum, image references/digests and licensing verification material. Customer packages require the public verification key; the signing private key belongs to the trusted licensing authority and must never be included.

Keep all bundle files together. A checksum can detect a changed payload, but it must be compared with a trusted release record rather than an untrusted checksum supplied beside a tampered file.

Offline scope

Bundled images can eliminate a registry download when the package and Docker runtime are complete. They do not make Telegram, online payments, remote VPN endpoints or online license checks function without internet access.

Both Windows and Linux read the local manifest, verify the deployment bundle and image archive, and load the bundled images when a complete local package is selected. An invalid local package fails validation rather than falling back to a network download. Prepare Docker, Compose, host tools and the release's license-verification prerequisites before disconnecting the network. An online retrieval path also exists; it is not the path for a disconnected installation.

For offline acceptance, test a fresh host with Docker prepared and external network unavailable. Confirm local image import, installation, setup and local router management. Test later reconnection separately. Record exactly which licensing mode and edition were used. A previously cached development installation is not a fresh offline-install test.

Related guides

Related guides: First-deployment walkthrough and success checklist, Deployment verification and first login, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback.