Management Interface: get_bundle¶
This command automatically downloads (almost) everything needed for an offline installation.
Note
You must be online and have your license.dat available when creating the install bundle.
Running get_bundle will pull down:
- The manage_server for the selected platform
- All Enterprise container images for the selected architecture and version
- Default server keys/certificates
...and bundle them together with:
- Your license.dat
- Any installers you have in ./installers, relative to the current directory (it does not, currently, download these automatically for you)
...into an enterprise_bundle.tar file. This file can then be moved to another host, unpacked, and used to install the server offline:
tar -xf enterprise_bundle.tar
cd enterprise_server
./manage_server install --offline
Typical Usage¶
You will generally want to just use get_bundle with defaults. But, if you're using manage_server on a separate machine from the one you're deploying the server to, it may be useful to manually specify some of the details, such as:
./manage_server get_bundle --platform linux --arch x86_64 -o enterprise_bundle.tar
Command Help¶
Get Enterprise server bundle as a .tar (for installing on an offline system)
Usage: manage_server get_bundle [OPTIONS]
Options:
--swarm[=<STACK_NAME>] Operate in docker swarm mode [env: ENTERPRISE_STACK_NAME=]
--tag <tag> Specify Enterprise server version
--platform <platform> Platform for Enterprise server management binary [default: macos] [possible values: linux, macos, windows]
--registry-host <HOSTNAME> Hostname of custom registry [env: ENTERPRISE_REGISTRY_HOST=registry.internal.v35.us] [default: registry.enterprise.binary.ninja]
--arch <arch> Architecture for Enterprise server images [default: aarch64] [possible values: x86_64, aarch64]
--registry-username <USER> Username for custom registry [env: ENTERPRISE_REGISTRY_USERNAME=]
-o, --output-file <output-file> Path to output file [default: enterprise_bundle.tar]
--registry-password <PASSWORD> Password for custom registry [env: ENTERPRISE_REGISTRY_PASSWORD=]
--docker-host <HOST> Overrides the default Docker/Podman Unix socket [env: DOCKER_HOST=]
--container-engine <ENGINE> Container engine to use for deployments (docker or podman) [env: ENTERPRISE_CONTAINER_ENGINE=docker] [default: docker] [possible values: docker, podman]
-l, --license-file <license-file> Path to Binary Ninja license file [env: ENTERPRISE_SERVER_LICENSE_FILE=] [default: license.dat]
-b, --license-bundle <license-bundle> Local path to Enterprise client floating license bundle [env: ENTERPRISE_SERVER_LICENSE_BUNDLE_FILE=] [default: license-bundle.b64]
--uid <uid> User ID used for data and tasks (defaults to current User ID) [env: ENTERPRISE_SERVER_UID=]
--gid <gid> Group ID used for data and tasks (defaults to current Group ID) [env: ENTERPRISE_SERVER_GID=]
-h, --help Print help
Database Options:
--db-name <NAME> Name of database to use [env: ENTERPRISE_DATABASE_NAME=] [default: binaryninja_enterprise]
--db-host <HOSTNAME> Name of host to use when connecting to database [env: ENTERPRISE_DATABASE_HOST=] [default: database]
--db-port <PORT> The port to use when connecting to database [env: ENTERPRISE_DATABASE_PORT=] [default: 5432]
--db-user <USERNAME> The user to use when connecting to database [env: ENTERPRISE_DATABASE_USER=] [default: binaryninja_enterprise]
--db-password-file <FILE> Path to file containing password to authenticate with the database [env: ENTERPRISE_DATABASE_PASSWORD_FILE=] [default: ./secrets/db_password]
Key-Value Store Options:
--redis-url <URL> URL to use when connecting to message broker [env: ENTERPRISE_KV_STORE_URL=] [default: redis://redis:6379]
Object Store Options:
--object-store-bucket-name <BUCKET> Object store bucket name (must be between 3 and 63 characters, only using lowercase letters, numbers, dot, and hyphen) [env: ENTERPRISE_OBJECT_STORE_BUCKET_NAME=] [default: binaryninja-enterprise]
--object-store-endpoint-url <URL> Object store endpoint URL [env: ENTERPRISE_OBJECT_STORE_URL=] [default: https://object-store:8333]
--object-store-access-key-file <FILE> Path to file containing the access key ID to use when authenticating with the object store [env: ENTERPRISE_OBJECT_STORE_ACCESS_KEY_FILE=] [default: ./secrets/object_store_access_key_id]
--object-store-secret-key-file <FILE> Path to file containing the secret access key to use when authenticating with the object store [env: ENTERPRISE_OBJECT_STORE_SECRET_KEY_FILE=] [default: ./secrets/object_store_secret_access_key]