Skip to main content

Routine checks

Review container health, disk capacity, certificate expiry, database integrity, image freshness, and unexpected campaign workloads.

Rebuild after updates

Clean inactive workloads

Remove application-owned target-browser containers:
Also remove all application-owned campaign workloads and isolated networks:
The second form is destructive and asks for confirmation when cli.confirm_destructive is enabled.

Reset images

reset stops application services and removes application-owned containers and configured Docker images. It preserves the database and stored campaign artifacts:
Use it only when a full image rebuild is intended.
Container logs are not part of persistent P-BitM storage and are lost when their containers are removed unless the Docker logging configuration sends them elsewhere.
Last modified on August 28, 2026