Page MenuHomeVyOS Platform

Move from fuse-overlayfs to native rootless overlay storage
Closed, ResolvedPublicFEATURE REQUEST

Description

Starting with Linux kernel version 5.13 podman can use a native overlay filesystem instead of relying on fuse-overlayfs which has significant performance improvements.

According to https://www.redhat.com/sysadmin/podman-rootless-overlay it does require running podman system reset to reset some metadata. Because VyOS does not support user data volumes, and requires binding to a source directory, I don't think we need to worry about data migration.

There are some notes of archlinux switching to kernel overlay in https://bugs.archlinux.org/task/71358

The VyOS path for the .has-mount-program file is:

/usr/lib/live/mount/persistence/container/storage/overlay/.has-mount-program

Details

Version
-
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Performance optimization

Event Timeline

syncer triaged this task as Wishlist priority.Jun 27 2024, 11:27 PM

This has been implemented for quit some time

Thanks for closing this out. Could you point to the commit or release that implemented it? I can't find it in the source on rolling:

  • src/conf_mode/container.py generate() renders data/templates/container/storage.conf.j2 to /etc/containers/storage.conf, with no other storage override.
  • That template still sets driver = "overlay" with mount_program = "/usr/bin/fuse-overlayfs"; its last change is 2023-05-28 (T5003, runroot), so it predates this task.
  • debian/control still depends on fuse-overlayfs.
  • The quadlet templates from T9129 (vyos-1x PR #5426) carry no storage settings, so the migration doesn't seem to change this.

Which Stream release would be the first to carry native overlay?
I'm on VyOS Stream 2026.03.

Context: on 2026.03 I hit overlay storage cleanup failures across reboots ("directory not empty", same symptom as containers/podman#23504) and moved all containers to vfs under /config as a workaround. I'd like to drop that once native overlay is actually in place, so knowing where it landed would help.