Prerequisites

CloudPeek is installed on a host from a signed installer bundle using the cpk command-line installer. Before you extract anything, check the host meets the requirements below and verify the bundle's signature.

What the target host needs

Docker Engine 29 or newer, with the Docker daemon running. The installer checks the daemon's version, so it reports the version as undetermined if Docker is installed but not started.
docker compose on PATH. The Compose plugin ships with current Docker Engine releases.
openssl on PATH, used at two points, each with its own minimum:
- Verifying the installer signature needs pkeyutl -rawin, which arrived in OpenSSL 3.0.
- Generating the self-signed TLS certificate during an HTTPS install needs req -addext, which arrived in OpenSSL 1.1.1. In practice: OpenSSL 3.0 or newer covers both.

Warning

If the signature check below reports -rawin as an unknown option, your openssl is too old. Upgrade it before continuing.

Note

Docker is the only thing the installer checks up front. openssl and docker compose are not verified, so a missing openssl surfaces only once the installer tries to generate the certificate — after you have answered every prompt. Confirm both are on PATH yourself before you start.

Chrome (or Chromium) and a matching chromedriver on PATH are needed only if you want to run the optional ./cpk verify smoke check after installing. They are not required to install or run CloudPeek.

Verify the installer signature

Alongside the installer tarball you will have received two more files:

cloudpeek-installer-v<version>-<platform>-<arch>.tar.gz.sig — the Ed25519 signature of the tarball.
cloudpeek-installer-v<version>-<platform>-<arch>.tar.gz.pub — the public key used to verify that signature.

<platform> is linux or macos, and <arch> is x86_64 or arm64, so a complete set of filenames looks like this:

cloudpeek-installer-v0.8.0-linux-x86_64.tar.gz
cloudpeek-installer-v0.8.0-linux-x86_64.tar.gz.sig
cloudpeek-installer-v0.8.0-linux-x86_64.tar.gz.pub

Place all three files in the same directory, then run:

openssl pkeyutl -verify -pubin \
  -inkey cloudpeek-installer-v0.8.0-linux-x86_64.tar.gz.pub -rawin \
  -in cloudpeek-installer-v0.8.0-linux-x86_64.tar.gz \
  -sigfile cloudpeek-installer-v0.8.0-linux-x86_64.tar.gz.sig

Warning

Authenticate the .pub key before you trust it. The three files arrive together, so an attacker who can substitute the tarball can substitute the signature and the public key with it — verification would then pass against the attacker's own key. Check the key you were sent against the fingerprint your CloudPeek contact gives you over a separate channel before running the command below. The signature check only proves the three files agree with each other.

You should see Signature Verified Successfully.

Warning

If you see Signature Verification Failure, do not proceed. The file has been tampered with or corrupted in transit. Re-download a fresh copy and try again.

Once the signature verifies, continue to Installing CloudPeek.

Installing CloudPeek: extract the bundle and run the installer.
Deployment Options: on-premises, air-gapped and hybrid models.
cpk Command Reference: every command the installer supports.

Prerequisites

What the target host needs

Verify the installer signature

Related