You are not logged in.
Hello,
I just upgraded the system, and when I went to restart the rootless containers, I got
Apr 23 23:57:36 podman[4621]: Error: kernel does not support overlay fs: kernel returned unlinkat /home/xxx/.local/share/containers
Installing `fuse-overlayfs` fixes the problem, but I'm pretty sure I did not have to install it and they were working correctly before.
My podman info:
graphDriverName: overlay
graphOptions: {}
graphRoot: /home/xxx/.local/share/containers/storage
graphRootAllocated: 2170820886528
graphRootUsed: 5813960704
graphStatus:
Backing Filesystem: zfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
The `Native Overlay Diff` is now false. Any idea what happened?
Linux xxx 6.1.25-1-lts #1 SMP PREEMPT_DYNAMIC Thu, 20 Apr 2023 14:01:39 +0000 x86_64 GNU/Linux
Last edited by Tid91 (2023-05-04 21:36:46)
Offline
The upload bumped podman to 4.5.0. Reverting to 4.4 makes native overlay work again:
graphDriverName: overlay
graphOptions: {}
graphRoot: /home/xxx/.local/share/containers/storage
graphRootAllocated: 2170811056128
graphRootUsed: 5814091776
graphStatus:
Backing Filesystem: zfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
Last edited by Tid91 (2023-04-23 23:10:54)
Offline
I rebooted, run `podman system migrate` and purged `fuse-overlayfs`, and only then it showed up properly.
Zfs is weird though (I use ext4):
https://github.com/containers/podman/issues/18315
https://github.com/openzfs/zfs/issues/8648
Offline
Yep, that's me in the github issue. It seems, since we have zfs < 2.2, we can't use native overlay support, and the fact that before it was working it was a bug.
Last edited by Tid91 (2023-05-04 21:37:10)
Offline