fix(kernel): files in overlayfs of container are missing

We found that when executing an overlay mount inside a Podman container, there is an issue: the middle layer contains a node_modules directory, but the upper layer cannot display this directory. When we disable all overlay options, it returns to normal. Currently, there are no other side effects found from disabling the overlay options. Signed-off-by: Kevin Cui <[email protected]>
oomol-lab · Oct 17, 2024 · 45c0095 · 45c0095
1 parent b68d96c
commit 45c0095
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 6 deletions.
diff --git a/kernel_external/configs/kernel_amd64_defconfig b/kernel_external/configs/kernel_amd64_defconfig
@@ -647,9 +647,7 @@ CONFIG_FUSE_FS=y
 CONFIG_CUSE=y
 CONFIG_VIRTIO_FS=y
 CONFIG_OVERLAY_FS=y
-CONFIG_OVERLAY_FS_INDEX=y
-CONFIG_OVERLAY_FS_XINO_AUTO=y
-CONFIG_OVERLAY_FS_METACOPY=y
+# CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW is not set
 CONFIG_FSCACHE=y
 CONFIG_CACHEFILES=y
 CONFIG_ISO9660_FS=y

diff --git a/kernel_external/configs/kernel_arm64_defconfig b/kernel_external/configs/kernel_arm64_defconfig
@@ -657,9 +657,7 @@ CONFIG_FUSE_FS=y
 CONFIG_CUSE=y
 CONFIG_VIRTIO_FS=y
 CONFIG_OVERLAY_FS=y
-CONFIG_OVERLAY_FS_INDEX=y
-CONFIG_OVERLAY_FS_XINO_AUTO=y
-CONFIG_OVERLAY_FS_METACOPY=y
+# CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW is not set
 CONFIG_FSCACHE=y
 CONFIG_CACHEFILES=y
 CONFIG_ISO9660_FS=y