As described here: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md#ensure-fuse-overlayfs-is-installed, it is recommended to use fuse-overlayfs in podman. That needs to have the fuse-overlayfs package pulled in as a dependency. Should this be a USE flag of libpod to pull in fuse-overlayfs?
Mabye we can make it conditional on the rootless USE flag, since it seems to be practically required for that.
I'm not sure about that... I've filed this before verifying overlayfs actually works for me and it ended up erroring out on me after configuring it in podman - it seems overlayfs is not supported on btrfs, or else I'm missing something (maybe in the kernel?). Since you can read online it should work, although I've also read (possibly outdated) it doesn't work well. I've proceeded with configuring "btrfs" for my storage in podman and that seems to work so far. That means overlayfs is not necessary if you have btrfs. And before this, I had it set to "vfs", which is another alternative for rootless... Although with suboptimal performance? I'm not really sure about the details as you can probably see :)
(In reply to Lukas Hrazky from comment #2) > I'm not sure about that... I've filed this before verifying overlayfs > actually works for me and it ended up erroring out on me after configuring > it in podman - it seems overlayfs is not supported on btrfs, or else I'm > missing something (maybe in the kernel?). Since you can read online it > should work, although I've also read (possibly outdated) it doesn't work > well. It's the kernel overlayfs driver that does not support btrfs. However, fuse-overlayfs does support btrfs. At least with libpod-1.8.2 I thought that it would choose fuse-overlayfs automatically but anyway you can configure it explicitly with a setting like this in ~/.config/containers/storage.conf: [storage] driver = "overlay" [storage.options] mount_program = "/usr/bin/fuse-overlayfs" > I've proceeded with configuring "btrfs" for my storage in podman and that > seems to work so far. > > That means overlayfs is not necessary if you have btrfs. And before this, I > had it set to "vfs", which is another alternative for rootless... Although > with suboptimal performance? I'm not really sure about the details as you > can probably see :) I had no idea that either btrfs or vfs were viable for rootless.
(In reply to Zac Medico from comment #3) > It's the kernel overlayfs driver that does not support btrfs. However, > fuse-overlayfs does support btrfs. That's weird, since it did give me that error... > At least with libpod-1.8.2 I thought that it would choose > fuse-overlayfs automatically ... Maybe it would, if I had fuse-overlayfs installed at the time the configuration was created? > ... but anyway you can configure it explicitly with a setting like > this in ~/.config/containers/storage.conf: > > [storage] > driver = "overlay" > [storage.options] > mount_program = "/usr/bin/fuse-overlayfs" That's what I did and got the error. I put "btrfs" there after that.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a0c6deb01e007307cba63a3dc3e307976608732f commit a0c6deb01e007307cba63a3dc3e307976608732f Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2020-04-19 22:49:34 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2020-04-19 22:53:32 +0000 app-emulation/libpod: Bump to version 1.9.0 #717394 add fuse? ( sys-fs/fuse-overlayfs ) dependency Closes: https://bugs.gentoo.org/717394 Reported-by: Lukas Hrazky <lukkash@email.cz> Closes: https://bugs.gentoo.org/717756 Reported-by: Dennis Schridde <devurandom@gmx.net> Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Zac Medico <zmedico@gentoo.org> app-emulation/libpod/Manifest | 1 + app-emulation/libpod/libpod-1.9.0.ebuild | 142 +++++++++++++++++++++++++++++++ app-emulation/libpod/metadata.xml | 4 + 3 files changed, 147 insertions(+)
(In reply to Lukas Hrazky from comment #4) > (In reply to Zac Medico from comment #3) > > It's the kernel overlayfs driver that does not support btrfs. However, > > fuse-overlayfs does support btrfs. > > That's weird, since it did give me that error... > > > At least with libpod-1.8.2 I thought that it would choose > > fuse-overlayfs automatically ... > > Maybe it would, if I had fuse-overlayfs installed at the time the > configuration was created? I've tested today with libpod-1.8.2 and it appeared to use fuse-overlayfs automatically after I wiped ~/.config/containers and ~/.local/share/containers. I also tested both btrfs and vfs in .config/containers/storage.conf, and they both worked fine in rootless mode. > > ... but anyway you can configure it explicitly with a setting like > > this in ~/.config/containers/storage.conf: > > > > [storage] > > driver = "overlay" > > [storage.options] > > mount_program = "/usr/bin/fuse-overlayfs" > > That's what I did and got the error. I put "btrfs" there after that. Ok, anyway, libpod-1.9.0 has fuse? ( sys-fs/fuse-overlayfs ) enabled by default.
