RunPod refuses images above a size line — measured: 10.1 GB boots, 14.5 GB is
'Exited by Runpod' two seconds after rent on every machine, no other reason
given. Container disk (tried 80 GB), layer format and the full image config were
each ruled out; size was the only difference. All five specialised images were
above the line.

They were above it for one reason: each was built on the full core, so it
carried 7 GB of CUDA, torch and triton the main venv never used on that pod,
beside the venv that did the work. The speaker image was 14.8 GB, of which
pyannote's own venv was 5.6.

The light core is coderai's Python dependencies with no GPU stack: 1.2 GB.
codai.api.app imports with no torch present (verified first), so the main
interpreter still boots the API, serves /healthz and /boot, and drives the
subprocess worker. A profile marked <name>.light builds on it, its main venv
carries only what the API layer needs, and the build FAILS if a torch reaches
that venv — because that is exactly the leak that would put the image back over
the line.

speaker: 14,796 MB -> 7,077 MB, complete, nothing on a volume.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY