pi05 image: python:3.12-slim base (pinned lerobot needs py>=3.12)

Dockerfile

@@ -6,9 +6,15 @@
 # Run with env MODEL_KIND matching the build arg (the arg only picks which
 # requirements file is installed; the env picks the adapter at boot).
 #
-# Base = the SAME proven torch stack as the Space (torch 2.5.1 + cu121); never
-# reinstall torch/torchvision/torchaudio on top (ABI break, see space/Dockerfile).
-FROM pytorch/pytorch:2.5.1-cuda12.1-cudnn9-runtime
+# Base per kind (BUILD_BASE arg):
+#   molmoact2 -> pytorch/pytorch:2.5.1-cuda12.1 (the proven Space stack; never
+#     reinstall torch/torchvision/torchaudio on top — ABI break, space/Dockerfile)
+#   pi05      -> python:3.12-slim (the pinned lerobot REQUIRES py>=3.12, which no
+#     pytorch/pytorch image ships; lerobot's own dep spec then installs the torch
+#     it wants — CUDA-bundled pip wheels, host driver via the endpoint runtime.
+#     This mirrors lelab's local venv, the combo the pi05 load path was proven on.)
+ARG BUILD_BASE=python:3.12-slim
+FROM ${BUILD_BASE}
 
 ARG MODEL_KIND=pi05
 

requirements-pi05.txt

@@ -1,7 +1,7 @@
-# MODEL_KIND=pi05 — installed ON TOP OF pytorch/pytorch:2.5.1-cuda12.1.
-# Do NOT list torch/torchvision/torchaudio (base image ships the matched trio;
-# pip may still try to bump torch via lerobot's spec — if the resolver fights,
-# add --no-deps discipline or constrain to the base image's torch).
+# MODEL_KIND=pi05 — installed on python:3.12-slim (BUILD_BASE arg in the
+# Dockerfile): the pinned lerobot REQUIRES py>=3.12, which no pytorch/pytorch
+# base ships. torch arrives via lerobot's own dep spec (CUDA-bundled pip
+# wheels) — do NOT pin torch here unless lerobot's resolver fights.
 #
 # lerobot pinned to the SAME commit as lelab's pyproject so a checkpoint trained
 # through our pipeline loads with identical code. The [pi] extra pulls the pi05