Uninstalling CloudPeek
cpk uninstall removes the running CloudPeek deployment from the host. It is destructive and deletes your data along with the software, so read what it removes before running it.
Uninstalling deletes the data volumes, which hold your database, uploaded files and everything CloudPeek has learned — incidents, investigations, wiki pages and runbooks. There is no undo. If you might want any of it back, export first.
Back up first (recommended)
If there is any chance you will want this instance again, take an export before uninstalling:
cd cloudpeek
./cpk export --save-dataThat writes an output_folder/ you can later restore with ./cpk import on this or another host. See Export and Import for the details, including the warning about handling the export as a secret.
Run the uninstall
From inside the cloudpeek/ directory:
cd cloudpeek
./cpk uninstallIt prints a warning and asks Continue? y/n. Only y proceeds — any other answer aborts and changes nothing. An empty answer re-asks rather than defaulting either way.
There is no unattended flag. Unlike ./cpk update -y, uninstall always asks for confirmation interactively, so it cannot be run non-interactively from a script.
What it removes
Everything CloudPeek started under the cloudpeek Docker Compose project:
- Containers — every CloudPeek container, force-removed even if running.
- Volumes — every CloudPeek data volume. This is the destructive part: Postgres data, MinIO object storage, Neo4j, ChromaDB and the rest.
- The
cloudpeekDocker network. - Images — the images those containers were running. This includes the third-party images (Postgres, Redis, MinIO, Neo4j, ChromaDB, OPA, Traefik, Zitadel), not just CloudPeek's own.
Because the third-party images are removed too, a later re-install has to fetch them again unless you are installing from an air-gapped bundle, which carries every image itself.
What it leaves behind
uninstall only touches Docker. The install directory stays on disk, including:
- the
cpkbinary, the compose file and the bundled image archive, and - the
.secrets/directory.
Remove the directory yourself once you are sure you are finished with the instance.
.secrets/ holds your credentials and the TLS certificate private key. Deleting the install directory is a security step, not just housekeeping — treat those files as secrets right up to the point you erase them.
Reinstalling afterwards
Uninstalling does not consume the installer bundle, so you can stand a fresh instance back up from the same directory.
uninstall leaves .secrets/ behind — still holding the previous instance's credentials and TLS private key — and install refuses to run when it finds those files. To reinstall in the same directory, either delete .secrets/ first, or run ./cpk install --force, which overrides that check and overwrites the old secrets with newly generated ones.
Forcing is the one case where that overwrite is harmless: uninstall already destroyed the data volumes, so nothing persisted is still expecting the previous credentials. On a live install, forcing would leave the new secrets disagreeing with the volumes and break it.
Answer the prompts as described in Installing CloudPeek. You will get an empty instance — to bring your old data back instead, use ./cpk import against an export you took earlier.
Related
- Export and Import: take a backup before you uninstall.
- Installing CloudPeek: standing a fresh instance back up.
- cpk Command Reference: every command the installer supports.