9:50 a.m.
Hi there,
This would also interest me. Although ZfsOnLinux has done significant steps
to make it possible, it doesn't seem to work fine yet. I wanted to use it
to delegate backups to users who own a particular Zpool (using sanoid), but
ended by customizing sudo commands and using znapzend as a backup daemon.
I also think that overlays is the right way to go.
Kind regards,
Le mer. 15 avr. 2020 à 15:54, Daniel Walsh <dwalsh(a)redhat.com> a écrit :
On 4/15/20 08:35, Ingvar.Bogdahn(a)itzbund.de wrote:
> Hello,
>
> I would like to know to which extent ZFS is supported as filesystem for
podmain containers.
>
> In particular, I'd like to know if it is possible to use ZFS clones as a
backend for the container filesystem layering and if zfs datasets are
usable for rootless containers (using zfs delegation). Is ZFS integration
done transparently, i.e. are zfs dataset clones created when a new layer is
created in a transparent way without explicit zfs commands?
>
> Thank you
>
>
> Best regards,
> Ingvar Bogdahn
>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
While we have support for this in container/storage, I have no idea how
many people use it. Most people use simple Overlayfs which I believe
will work on top of zfs.
I am also not sure if ZFS will work as a backend in rootless mode. We
use fuse-overlay to make this possible, so if you are attempting to run
rootless, this might also be a concern.
The Linux kernel currently only allows not root users inside of a user
namespace to mount certain types of file systems.
procfs, tmpfs, bind, sysfs, and fuse (I believe this is the currently
limit).
So if zfs cloning requires a mount it will probably not work.
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io