dev-new: lab's podman needs /run/lab after reboot #442

Open
opened 2026-10-08 08:12:24 +02:00 by dominik.polakovics · 0 comments

After a reboot of dev-new, /run/lab was missing and lab could not start containers until it was recreated by hand.

Cause: the lab service's podman db (/var/lib/lab/.local/share/containers/storage/db.sql, store created 2026-07-25) predates coding-lab ADR-0060 (2026-07-26) and still records runroot /run/lab/containers and tmpdir /run/lab/libpod/tmp. Podman keeps using those recorded paths. /run is tmpfs and root-owned, so after a boot the lab user cannot recreate the directory. Before this reboot, /run/lab was still left over from the old RuntimeDirectory=lab layout.

Short term: recreate /run/lab (owned by lab) at every boot via tmpfiles.
Real fix: run upstream's documented one-time migration podman system reset --force as the lab user (see coding-lab docs/ops.md). It wipes local containers and images, so do it while no container runs are live. After that the tmpfiles rule can be dropped.

After a reboot of dev-new, `/run/lab` was missing and lab could not start containers until it was recreated by hand. Cause: the lab service's podman db (`/var/lib/lab/.local/share/containers/storage/db.sql`, store created 2026-07-25) predates coding-lab ADR-0060 (2026-07-26) and still records runroot `/run/lab/containers` and tmpdir `/run/lab/libpod/tmp`. Podman keeps using those recorded paths. `/run` is tmpfs and root-owned, so after a boot the `lab` user cannot recreate the directory. Before this reboot, `/run/lab` was still left over from the old `RuntimeDirectory=lab` layout. Short term: recreate `/run/lab` (owned by lab) at every boot via tmpfiles. Real fix: run upstream's documented one-time migration `podman system reset --force` as the `lab` user (see coding-lab docs/ops.md). It wipes local containers and images, so do it while no container runs are live. After that the tmpfiles rule can be dropped.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Cloonar/nixos#442
No description provided.