Skip to content

fix: always enable production vfs fallback - #13

Closed
neebs12 wants to merge 4 commits into
mainfrom
fix/always-vfs-fallback
Closed

neebs12 wants to merge 4 commits into
mainfrom
fix/always-vfs-fallback

Conversation

@neebs12

@neebs12 neebs12 commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • always try vfs after the preferred Docker storage driver fails
  • remove the production opt-in flag and accept a validated vfs daemon
  • exercise the default fallback path in unit and real ARM64 image smoke tests
  • document overlay2 as preferred and vfs as a supported production fallback

Validation

  • npm run check
  • npm run test:image
  • shellcheck scripts/*.sh test/scripts/*.sh
  • reproducible runner image artifact check
  • stale fallback-policy documentation scan

@neebs12

neebs12 commented Jul 6, 2026

Copy link
Copy Markdown
Owner Author

Verified in PR CI and integrated into the rewritten single root commit on main.

@neebs12 neebs12 closed this Jul 6, 2026
@neebs12
neebs12 deleted the fix/always-vfs-fallback branch July 6, 2026 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant