Just the basics to get the container running:
docker run --rm hotio/mergerfs ...The default ENTRYPOINT is mergerfs -f.
| Tag | Description | Build Status | Last Updated |
|---|---|---|---|
| latest | The same as stable |
||
| stable | Stable version |  |
 |
| unstable | Every commit to master branch |  |
 |
You can also find tags that reference a commit or version number.
By setting the bind-propagation to shared on the volume mountpoint, like this -v /data/mountpoint:/mountpoint:shared, you are able to access the mount from the host. If you want to use this mount in another container, the best solution is to create a volume on the parent folder of that mount with bind-propagation set to slave. For example, -v /data:/data:slave (/data on the host, would contain the previously created volume mountpoint). Doing it like this will ensure that when the container creating the mount restarts, the other containers using that mount will recover and keep working.
In most cases you will need some or all of the following flags added to your command to get the required docker privileges when using a mergerfs mount.
--security-opt apparmor:unconfined --cap-add SYS_ADMIN --device /dev/fuse