docker run. Suited to teams with a single node of 1~8 GPUs.
Configuration
Key semantics
Atomic GPU allocation
Atomic GPU allocation
GPU selection and container launch happen under the same lock, and the source of truth for allocation lives in container labels — after a console restart, the usage view is rebuilt from
docker ps, so “ghost GPU occupation” cannot happen.Container reclamation
Container reclamation
After reconciliation confirms a terminal state, the platform archives any backend-only tail logs and immediately deletes the container.
FORGE_LOCAL_CONTAINER_TTL_S only reaps orphans left by control-plane failures.Images
Images
Resolution order is per-job
--image → framework default → runtime registry → catalog. Tags work; prefer a digest for production reproducibility. User images must satisfy FORGE_ALLOWED_IMAGE_REGISTRIES.No-NVIDIA environments (testing only)
No-NVIDIA environments (testing only)
FORGE_LOCAL_GPU_PASSTHROUGH=0 simulation mode: allocation / accounting / labels work as usual, but containers launch without --gpus. For E2E and dev machines; production must keep the default passthrough.