fix: wipe the pre-seeded podman storage before build #11

Merged

mlvtito merged 1 commit from fix/podman-fresh-storage into main

2026-11-15 21:49:39 +00:00

hermes_forgeron commented

2026-11-15 21:42:14 +00:00

Collaborator

Third iteration on #7 — this time the two failures are consistent with each other and point at the real root cause.

Evidence

Run after PR #8 (no storage.conf): database graph driver "overlay" does not match our graph driver "vfs" at build.
Run after PR #10 (valid vfs storage.conf read before ANY podman command, including login): same error at build.

If the overlay database had been created by podman login, the second run would have created a fresh vfs database instead. The only remaining explanation: quay.io/podman/stable ships a pre-initialized graph root with the overlay driver, and podman 5 refuses driver switches against an existing database — the driver = "vfs" from storage.conf only applies at database creation time, never retroactively.

Fix

Wipe the pre-seeded graph root before any podman command:

rm -rf /var/lib/containers

combined with the existing vfs storage.conf, podman then creates a fresh vfs database used consistently by login, build and push. The pre-seeded overlay storage is only there to make podman-in-podman work out of the box — we do not need it.

Wiki updates on merge

Nothing to update in the Wiki.

Third iteration on #7 — this time the two failures are consistent with each other and point at the real root cause. ## Evidence - Run after PR #8 (no storage.conf): `database graph driver "overlay" does not match our graph driver "vfs"` at build. - Run after PR #10 (valid vfs storage.conf read before ANY podman command, including login): **same error at build**. If the overlay database had been created by `podman login`, the second run would have created a fresh vfs database instead. The only remaining explanation: **`quay.io/podman/stable` ships a pre-initialized graph root with the overlay driver**, and podman 5 refuses driver switches against an existing database — the `driver = "vfs"` from storage.conf only applies at database creation time, never retroactively. ## Fix Wipe the pre-seeded graph root before any podman command: ```sh rm -rf /var/lib/containers ``` combined with the existing vfs storage.conf, podman then creates a fresh vfs database used consistently by login, build and push. The pre-seeded overlay storage is only there to make podman-in-podman work out of the box — we do not need it. ## Wiki updates on merge Nothing to update in the Wiki.

hermes_forgeron added 1 commit

2026-11-15 21:42:14 +00:00

fix: wipe the pre-seeded podman storage before build c28edc682a

quay.io/podman/stable ships a pre-initialized graph root with the
overlay driver, and podman 5 refuses driver switches against an
existing database. The vfs storage.conf could not apply over it.
Deleting /var/lib/containers first forces a fresh vfs DB for the
whole run (login, build, push).