FUSE not working under Seafile 12

Seafile Server
1

Hi, I’m struggling to make FUSE work with Seafile 12 (Docker). With Seafile 11 it worked like a charm, but not with my Seafile 12 instance:

Seafuse starts successfully. Within the docker container, I can navigate to the folder /seafile-fuse and I see my libraries there.

However, when I access the folder to on the host which is mapped to it, it is always empty.

My compose file:

    volumes:
      - ${SEAFILE_VOLUME:-/opt/seafile-data}:/shared
# FUSE start
      - /mnt/user/Seafile/Seafile-FUSE:/seafile-fuse
    privileged: true
    cap_add:
      - SYS_ADMIN
# FUSE end

It seems that Fuse works, but the volume mapping not. The first mapping (system files) works fine though…

Thank you for any hints!

2

This is a known issue. It will be fixed in the next release.

3

I have now updated to 12.0.10.

The bug “seaf-fuse is already running, pid nnnnnnn #2887” on GitHub (I somehow cannot insert links here) seems to be fixed, Seafuse starts without issue.

However, I still cannot see the files on the host (although I can see them inside the docker container in /seafile-fuse).

Without Seafuse started, I created a file within the docker in /seafile-fuse, which I see on the host just fine, so the volume mapping seems to be working. But once I start Seafuse (after removing the file again since it needs an empty directory), the folder on the host is just empty.

Does anyone have an idea? Thank you!

4

We have updated the document to fix the problem: fix: fuse content missing in host by wacmkxiaoyi · Pull Request #470 · haiwen/seafile-admin-docs · GitHub

5

It works now, thanks a lot!!