dev-new: lab's podman needs /run/lab after reboot #442
Labels
No labels
bug
enhancement
in-progress
needs-info
needs-triage
p0
ready-for-agent
ready-for-human
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/nixos#442
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After a reboot of dev-new,
/run/labwas 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/containersand tmpdir/run/lab/libpod/tmp. Podman keeps using those recorded paths./runis tmpfs and root-owned, so after a boot thelabuser cannot recreate the directory. Before this reboot,/run/labwas still left over from the oldRuntimeDirectory=lablayout.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 --forceas thelabuser (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.