fix: pin podman storage driver to vfs before any podman command #9

Merged

mlvtito merged 1 commit from fix/image-storage-driver into main

2026-11-15 20:55:55 +00:00

hermes_forgeron commented

2026-11-15 20:51:49 +00:00

Collaborator

Follow-up to #7: the first dispatch failed at Build and push image with

Error: database graph driver "overlay" does not match our graph driver "vfs": database configuration mismatch

Root cause

podman login (which succeeded — so BOT_TOKEN has the package write scope) was the first podman command: it initialized podman's storage database with the default overlay driver. The subsequent podman build --storage-driver=vfs then refused the mismatch.

Fix

A new step right after the package install writes /etc/containers/storage.conf with driver = "vfs" (plus an explicit runroot) before any podman command runs — login, build and push now share the same storage database. The explicit --storage-driver=vfs on the build stays as documentation.

Wiki updates on merge

Nothing to update in the Wiki (implementation detail of the workflow; the storage choice is documented in the workflow itself).

Follow-up to #7: the first dispatch failed at `Build and push image` with ``` Error: database graph driver "overlay" does not match our graph driver "vfs": database configuration mismatch ``` ## Root cause `podman login` (which succeeded — so `BOT_TOKEN` has the package write scope) was the first podman command: it initialized podman's storage database with the **default `overlay`** driver. The subsequent `podman build --storage-driver=vfs` then refused the mismatch. ## Fix A new step right after the package install writes `/etc/containers/storage.conf` with `driver = "vfs"` (plus an explicit runroot) **before any podman command runs** — login, build and push now share the same storage database. The explicit `--storage-driver=vfs` on the build stays as documentation. ## Wiki updates on merge Nothing to update in the Wiki (implementation detail of the workflow; the storage choice is documented in the workflow itself).

hermes_forgeron added 1 commit

2026-11-15 20:51:49 +00:00

fix: pin podman storage driver to vfs before any podman command 27bca2ee53

The first podman invocation (login) initialized the storage database
with the default overlay driver, so the subsequent vfs build failed
with a database configuration mismatch. A storage.conf written before
any podman command keeps login, build and push consistent.