fix: redirect the podman graphroot to a fresh path #12
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/podman-graphroot"
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?
Fourth iteration on #7. The previous
rm -rf /var/lib/containersfailed because that path is a mount point:quay.io/podman/stabledeclaresVOLUME /var/lib/containers, and act_runner mounts an anonymous volume there — so deletion fails withDevice or resource busy.Fix
Stop fighting the mount: point the graphroot at a fresh path in
storage.conf: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-storagethat login, build and push share consistently. Config validated with a TOML parser before pushing.Wiki updates on merge
Nothing to update in the Wiki.