Fuse-xfs is a MacFuse (OSXFUSE) driver for XFS filesystems. This driver allows Mac OS 10.7 with OSXFUSE/MacFuse to mount XFS filesystems in readonly mode. The journal is ignored, but basic read only operations should work fine. 1) Start the run.sh script in src/zfs-fuse. This will start the main zfs-fuse daemon process that must be running at all times. You should be running it with root permissions. Currently ZFS-FUSE is configured to use up to 128 MB of RAM, but it can grow larger with some usage patterns. It's recommended to have a machine with at least 1 GB of RAM. What is FUSE?¶ FUSE is a userspace filesystem framework. It consists of a kernel module (fuse.ko), a userspace library (libfuse.) and a mount utility (fusermount). One of the most important features of FUSE is allowing secure, non-privileged mounts. This opens up new possibilities for the use of filesystems.

For more details on Fuse Tooling features, see the Tooling User Guide. Here is a summary of the tutorials and what you accomplish in each one: Chapter 2, Setting up your environment Create a Fuse Integration project and set up the tutorial resource files. When you create a project, it auto-creates a routing context and a preliminary route. You need a specific fuse driver for each file system type, as the point of fuse is to have the file system code running in user-land. So any pre-existing kernel driver code, running in kernel-land (ext2, ext3, ext4, xfs.) can't be used 'as-is' by fuse.

Estimated reading time: 10 minutes

Ideally, very little data is written to a container’s writable layer, and youuse Docker volumes to write data. However, some workloads require you to be ableto write to the container’s writable layer. This is where storage drivers comein.

Docker supports several different storage drivers, using a pluggablearchitecture. The storage driver controls how images and containers are storedand managed on your Docker host.

After you have read the storage driver overview, thenext step is to choose the best storage driver for your workloads. In makingthis decision, there are three high-level factors to consider:

If multiple storage drivers are supported in your kernel, Docker has a prioritized list of which storage driver to use if no storage driver is explicitly configured, assuming that the storage driver meets the prerequisites.

Use the storage driver with the best overall performance and stability in the most usual scenarios.

Docker supports the following storage drivers:

overlay2 is the preferred storage driver, for all currently supported Linux distributions, and requires no extra configuration.
aufs was the preferred storage driver for Docker 18.06 and older, when running on Ubuntu 14.04 on kernel 3.13 which had no support for overlay2.
fuse-overlayfs is preferred only for running Rootless Dockeron a host that does not provide support for rootless overlay2.On Ubuntu and Debian 10, the fuse-overlayfs driver does not need to beused overlay2 works even in rootless mode.See Rootless mode documentation.
devicemapper is supported, but requires direct-lvm for production environments, because loopback-lvm, while zero-configuration, has very poor performance. devicemapper was the recommended storage driver for CentOS and RHEL, as their kernel version did not support overlay2. However, current versions of CentOS and RHEL now have support for overlay2, which is now the recommended driver.
The btrfs and zfs storage drivers are used if they are the backingfilesystem (the filesystem of the host on which Docker is installed).These filesystems allow for advanced options, such as creating “snapshots”,but require more maintenance and setup. Each of these relies on the backingfilesystem being configured correctly.
The vfs storage driver is intended for testing purposes, and for situationswhere no copy-on-write filesystem can be used. Performance of this storagedriver is poor, and is not generally recommended for production use.

Docker’s source code defines the selection order. You can see the order atthe source code for Docker Engine 20.10

If you run a different version of Docker, you can use the branch selector at the top of the file viewer to choose a different branch.

Some storage drivers require you to use a specific format for the backing filesystem. If you have external requirements to use a specific backing filesystem, this may limit your choices. See Supported backing filesystems.

After you have narrowed down which storage drivers you can choose from, your choice is determined by the characteristics of your workload and the level of stability you need. See Other considerationsfor help in making the final decision.

NOTE: Your choice may be limited by your operating system and distribution. For instance, aufs is only supported on Ubuntu and Debian, and may require extra packages to be installed, while btrfs is only supported on SLES, which is only supported with DockerEnterprise. See Support storage drivers per Linux distribution for more information.

Supported storage drivers per Linux distribution

At a high level, the storage drivers you can use is partially determined bythe Docker edition you use.

In addition, Docker does not recommend any configuration that requires you todisable security features of your operating system, such as the need to disableselinux if you use the overlay or overlay2 driver on CentOS.

Docker Engine - Community

For Docker Engine - Community, only some configurations are tested, and your operatingsystem’s kernel may not support every storage driver. In general, the followingconfigurations work on recent versions of the Linux distribution:

Linux distribution	Recommended storage drivers	Alternative drivers
Docker Engine - Community on Ubuntu	`overlay2` or `aufs` (for Ubuntu 14.04 running on kernel 3.13)	`overlay`¹, `devicemapper`², `zfs`, `vfs`
Docker Engine - Community on Debian	`overlay2` (Debian Stretch), `aufs` or `devicemapper` (older versions)	`overlay`¹, `vfs`
Docker Engine - Community on CentOS	`overlay2`	`overlay`¹, `devicemapper`², `zfs`, `vfs`
Docker Engine - Community on Fedora	`overlay2`	`overlay`¹, `devicemapper`², `zfs`, `vfs`

¹) The overlay storage driver is deprecated, and will be removed in a futurerelease. It is recommended that users of the overlay storage driver migrate to overlay2.

²) The devicemapper storage driver is deprecated, and will be removed in a futurerelease. It is recommended that users of the devicemapper storage driver migrateto overlay2.

Note

The comparison table above is not applicable for Rootless mode.For the drivers available in Rootless mode, see the Rootless mode documentation.

Fuse-xfs Mount

When possible, overlay2 is the recommended storage driver. When installingDocker for the first time, overlay2 is used by default. Previously, aufs wasused by default when available, but this is no longer the case. If you want touse aufs on new installations going forward, you need to explicitly configureit, and you may need to install extra packages, such as linux-image-extra.See aufs.

On existing installations using aufs, it is still used.

When in doubt, the best all-around configuration is to use a modern Linuxdistribution with a kernel that supports the overlay2 storage driver, and touse Docker volumes for write-heavy workloads instead of relying on writing datato the container’s writable layer.

The vfs storage driver is usually not the best choice. Before using the vfsstorage driver, be sure to read aboutits performance and storage characteristics and limitations.

Expectations for non-recommended storage drivers: Commercial support isnot available for Docker Engine - Community, and you can technically use any storage driverthat is available for your platform. For instance, you can use btrfs withDocker Engine - Community, even though it is not recommended on

Fuse Xfs