[GH-ISSUE #401] Docker run onlyoffice/documentserver fails on ZFS #207

Open
opened 2026-02-26 10:30:58 +03:00 by kerem · 3 comments
Owner

Originally created by @baldrianbandit on GitHub (Jan 29, 2022).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/401

Bug: docker run onlyoffice/documentserver failes when data-root of docker on a ZFS device.

Steps to reproduce:

  • create a new pool zpool create -m /mnt/pool tank /dev/disk/by-id/<disk>
  • in /etc/docker/deamon.json, set "data-root": "/mnt/pool"
  • restart docker systemctl restart docker
  • execute docker run onlyoffice/documentserver

Error message from docker: Daemon failed to copy files.

5.16.3-arch1-1
docker 1:20.10.12-1
onlyoffice/documentserver latest and :6.4

Further information

When docker detects its data root on a ZFS device, it automatically switches its storage driver from overlay2 to zfs. Forcing docker to use overlay2 by setting "storage-driver": "overlay2" makes starting of docker.service fail: "unknown storage driver". Docker being unable to ignore the filesystem type it has its data root on might be the real issue here.

Workaround

Using a data root on an ext4 partition makes docker run execute without errors.

Originally created by @baldrianbandit on GitHub (Jan 29, 2022). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/401 **Bug: docker run onlyoffice/documentserver failes when data-root of docker on a ZFS device.** Steps to reproduce: - create a new pool `zpool create -m /mnt/pool tank /dev/disk/by-id/<disk>` - in /etc/docker/deamon.json, set `"data-root": "/mnt/pool"` - restart docker `systemctl restart docker` - execute `docker run onlyoffice/documentserver ` Error message from docker: Daemon failed to copy files. 5.16.3-arch1-1 docker 1:20.10.12-1 onlyoffice/documentserver latest and :6.4 **Further information** When docker detects its data root on a ZFS device, it automatically switches its storage driver from overlay2 to zfs. Forcing docker to use overlay2 by setting `"storage-driver": "overlay2"` makes starting of docker.service fail: "unknown storage driver". Docker being unable to ignore the filesystem type it has its data root on might be the real issue here. **Workaround** Using a data root on an ext4 partition makes `docker run` execute without errors.
Author
Owner

@ShockwaveNN commented on GitHub (Jan 29, 2022):

Hi, I have absolutely no experience with ZFS, but just thinking logically and reading your report - didn't error on docker run before DocumentServer even able to initialize it (if I got you right) - didn't this is Docker issue, not ours?

<!-- gh-comment-id:1024952413 --> @ShockwaveNN commented on GitHub (Jan 29, 2022): Hi, I have absolutely no experience with ZFS, but just thinking logically and reading your report - didn't error on docker run before DocumentServer even able to initialize it (if I got you right) - didn't this is Docker issue, not ours?
Author
Owner

@baldrianbandit commented on GitHub (Feb 2, 2022):

Well, other images like helloworld or collabora/code actually do run using this ZFS setup, so the issue seems to be specific to onlyoffice/documentserver. On the other hand, since I cannot get more verbosity out of docker in this case, I can't point to the root of the issue.

I'm fine running docker on an ext4 partition. Let's leave the dissue for documentary purpose and see if someone (not) confirms.

<!-- gh-comment-id:1028130301 --> @baldrianbandit commented on GitHub (Feb 2, 2022): Well, other images like helloworld or collabora/code actually do run using this ZFS setup, so the issue seems to be specific to onlyoffice/documentserver. On the other hand, since I cannot get more verbosity out of docker in this case, I can't point to the root of the issue. I'm fine running docker on an ext4 partition. Let's leave the dissue for documentary purpose and see if someone (not) confirms.
Author
Owner

@ShockwaveNN commented on GitHub (Feb 2, 2022):

@baldrianbandit Fair enough, I'll leave this issue opened

Maybe it has something done with mounts or like this, not sure

<!-- gh-comment-id:1028142877 --> @ShockwaveNN commented on GitHub (Feb 2, 2022): @baldrianbandit Fair enough, I'll leave this issue opened Maybe it has something done with mounts or like this, not sure
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#207
No description provided.