--container

CLI: --container
REST: CLI only

Sets ZShot up to run inside a container. Pass it in place of the individual switches.

Setting	Effect
Sandbox	Stays on where the runtime permits it; otherwise ZShot renders without it and prints a warning. Hardening has the seccomp profile that keeps it on under Docker.
Shared memory	Chromium uses a temp file instead of `/dev/shm`, which most runtimes keep small.
GPU	On Linux, without a render node at `/dev/dri/renderD*`, rendering falls back to software. Map one in with `--device /dev/dri`; `--software-rendering` forces software rendering regardless.
License	An activation made during the run is released at exit instead of saved to the config file.

Licenses in Disposable Containers

Each fresh container has its own machine identifier, so it takes an activation slot. With --container the run activates on start and releases on exit, so the next container reuses the slot.

Example

CLI Run locally

zshot -f pipeline.png --container \
  --license-key "$ZSHOT_LICENSE" \
  https://zshot-cli.com/example_assets/zrm/