> ## Documentation Index
> Fetch the complete documentation index at: https://p-bitm-2269ecee.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Session containers

> Understand browser image selection, readiness, identity, isolation, and capacity limits.

P-BitM creates one browser container for each active victim session. Each
victim session represents one authorized target browser.

## Images

* `bitm-vnc:latest` provides the VNC-based browser runtime.
* `bitm-selkies:latest` provides the Selkies streaming runtime selected for
  the host architecture.

The selected campaign protocol determines which image is used. Image names and
Dockerfiles are configured in `config.yaml`.

## Readiness

After creation, the admin backend waits for the container-specific readiness
signal up to `VICTIM_READY_TIMEOUT_SECONDS`. A container that exists but is not
ready is not presented as a usable live session.

## Identity and isolation

Containers and networks carry application labels. Management operations verify
campaign ID, `victim_id`, and role labels before executing or removing a
workload. Campaign networks isolate unrelated campaigns.

## Limits

Per-campaign admission and host-wide active-session limits protect runtime
capacity. Configure these according to measured host resources rather than
disabling them.