fix: redirect the podman graphroot to a fresh path #12

Merged
mlvtito merged 1 commit from fix/podman-graphroot into main 2026-11-15 21:55:22 +00:00
Collaborator

Fourth iteration on #7. The previous rm -rf /var/lib/containers failed because that path is a mount point: quay.io/podman/stable declares VOLUME /var/lib/containers, and act_runner mounts an anonymous volume there — so deletion fails with Device or resource busy.

Fix

Stop fighting the mount: point the graphroot at a fresh path in storage.conf:

[storage]
driver = "vfs"
graphroot = "/tmp/containers-storage"
runroot = "/tmp/containers-runroot"

The pre-seeded overlay database is then simply ignored (it lives in the old graph root), and podman creates a brand-new vfs database under /tmp/containers-storage that login, build and push share consistently. Config validated with a TOML parser before pushing.

Wiki updates on merge

Nothing to update in the Wiki.

Fourth iteration on #7. The previous `rm -rf /var/lib/containers` failed because that path is a **mount point**: `quay.io/podman/stable` declares `VOLUME /var/lib/containers`, and act_runner mounts an anonymous volume there — so deletion fails with `Device or resource busy`. ## Fix Stop fighting the mount: point the **graphroot** at a fresh path in `storage.conf`: ```toml [storage] driver = "vfs" graphroot = "/tmp/containers-storage" runroot = "/tmp/containers-runroot" ``` The pre-seeded overlay database is then simply ignored (it lives in the old graph root), and podman creates a brand-new vfs database under `/tmp/containers-storage` that login, build and push share consistently. Config validated with a TOML parser before pushing. ## Wiki updates on merge Nothing to update in the Wiki.
/var/lib/containers is a VOLUME in quay.io/podman/stable, so it cannot
be deleted (Device or resource busy). Instead of fighting the mount,
point graphroot at a fresh /tmp path in storage.conf: the pre-seeded
overlay database is ignored and podman creates a new vfs DB used by
login, build and push.
Sign in to join this conversation.
No reviewers
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
serious-devs/ai-factory!12
No description provided.