From dc2c5ed31d0443a61444292279f85c29b096d7c8 Mon Sep 17 00:00:00 2001 From: Christian Breunig Date: Sun, 11 Oct 2026 09:36:57 +0200 Subject: container: T9456: use kernel overlayfs unless storage sits on overlayfs Since T5003 every system was configured to mount container storage via fuse-overlayfs. This is only needed on live boot, where the storage sits on the root overlayfs and podman refuses native overlay. Installed systems keep it on the persistence partition and paid for a userspace FUSE process per container plus a round trip on every file operation. The mount program is now only configured when the storage is backed by overlayfs, otherwise the kernel overlay driver is used. Existing storage keeps using fuse-overlayfs: podman records that a mount program was used, as its layers store whiteouts in a format the kernel driver does not understand. Moving such a system to kernel overlayfs requires resetting the container storage and re-pulling all images. --- python/vyos/defaults.py | 1 + 1 file changed, 1 insertion(+) (limited to 'python') diff --git a/python/vyos/defaults.py b/python/vyos/defaults.py index 23243346d..4421c3636 100644 --- a/python/vyos/defaults.py +++ b/python/vyos/defaults.py @@ -67,6 +67,7 @@ frr_debug_enable = '/tmp/vyos.frr.debug' dhclient_debug_enable = '/tmp/vyos.dhclient.debug' static_route_dhcp_interfaces_path = '/tmp/static_dhcp_interfaces' vyos_configd_socket_path = 'ipc:///run/vyos-configd.sock' +podman_mount_program = '/usr/bin/fuse-overlayfs' cfg_group = 'vyattacfg' -- cgit v1.2.3