chore: drop redundant STORAGE_DRIVER/BUILDAH_ISOLATION env vars in build-push.yaml #41
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?
The job-level
envblock in.forgejo/workflows/build-push.yamlsets:Both were added as belt-and-suspenders before the storage.conf-based approach landed (#38,
fix/buildah-vfs-storage-conf). Now that/etc/containers/storage.confpinsdriver = "vfs"authoritatively for both buildah and podman, these env vars are redundant — the conf file is what actually does the coercion (the env var alone wasn't enough; podman reads prior driver metadata from the storage path before consulting the env, which is what triggered the original overlay-on-overlayfs failure).Drop the env vars from the
jobs.build-push.envblock once we've seen ~3-4 successful build-push runs againstmainto confirm nothing else regresses.