Comment 1 Nico Gulden 2017-07-12 09:12:37 CEST

Requested again: Ticket#2017070721000618. In this case, the missing ZFS is a blocker for using UCS.

Comment 2 Daniel Tröder 2017-07-12 09:17:36 CEST

I think there is a problem with ZFS and docker.

@Dirk: can docker be forced to use an aufs (or whatever overlay fs is currenty in use) even if it detects zfs as the on-disk format?

Comment 3 Philipp Hahn 2017-07-18 15:33:05 CEST

Debian-Stretch has <https://tracker.debian.org/pkg/zfs-linux> - please contact me before integrating that into UCS as maintaining it with the Linux-Kernel need coordination.

(In reply to Daniel Tröder from comment #2)
> I think there is a problem with ZFS and docker.

Read <https://integratedcode.us/2016/08/30/storage-drivers-in-docker-a-deep-dive/> (and <https://github.com/AkihiroSuda/issues-docker>)

> @Dirk: can docker be forced to use an aufs (or whatever overlay fs is
> currenty in use) even if it detects zfs as the on-disk format?

From my reading you DO NOT want to use overlayfs or aufs on top of btrfs or zfs, but use specific drivers for those FSs, as they already provide the features added by those overlay FSs. But btrfs and zfs have the draw-back of not having the "memory sharing capabilities" and seem to be slower.

Comment 4 Ingo Steuwer 2020-07-03 20:52:26 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.

Comment 5 Philipp Hahn 2020-07-04 08:59:39 CEST

Asked for in TT 2020-06-25/26
At least re-enable btrfs?