WSL: SSHFS remote file system mount failure

Having issues mounting a remote file system using sshfs fuse seems to be failing to find the device

root@localhost:~# sshfs m@192.168.1.12:/home/m/ /root/mount/
fuse: device not found, try 'modprobe fuse' first
root@localhost:~# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.4.0+/modules.dep.bin'
root@localhost:~#

About this issue

  • Original URL
  • State: closed
  • Created 11 years ago
  • Reactions: 31
  • Comments: 26 (3 by maintainers)

Most upvoted comments

WSL should definitely support fuse, this is a main use case. I expect to sshfs mount remote filesystem and access it both from bash and from windows file explorer at the same time. It should appear to windows file explorer as part of the folder tree.

+1 for fuse !

I am taking a run at fixing this. Cross your fingers and I’ll report back if I find joy.

Never saying never, but no plans to support this feature in the appreciable future. Moving to backlog for now.

If you’d like us to reconsider, please find/update this issue on UserVoice.

Just sayin’

image

Don’t get too excited though. This probably isn’t going any further than a PoC. It would need a lot of work to be useful. I just wanted to see if it could be done.

@basnijholt We always intended this repo to track bugs that we aim to fix. This is an ask for a feature that we have not currently implemented FUSE support and have no immediate plans to do so. As such, there’s no actionable issue to track, so this issues was closed, with a request that interested parties upvote the ask on UserVoice (which better handles voting than GitHub currently does).

@HenkPoley kindly followed-up with specific links to relevant UserVoice asks for those interested in voting.

FUSE is available in WSL2.

How to hide bugs under the carpet

When bugs becomes features… virtual features or feature request…

UserVoice items for:

Note that SMB/CIFS mounting is already implemented. Might be useful for some of the followers of this ticket.

Why is this issue closed? It doesn’t seem to be fixed.

FUSE is statically compiled into the WSL2 kernel. In general modprobe is not applicable in WSL2 by-design, unless you off-road it with your own compiled modules. Here the fuse module is built-in.

4.4.0-19041-Microsoft

You are not on WSL2. You can list your installed distributions and versions with wsl.exe -l -v.

@bitcrazed the UserVoice links are dead. Does WSL have an alternative feature voting system it would prefer? I would like to vote for this feature.

I am taking a run at fixing this. Cross your fingers and I’ll report back if I find joy.

need any help?

You cannot load Linux kernel modules on WSL, and probably never will.

Though something like fuse (user mode filesystems), or say USB usermode access would be really nice to have.

FUSE is available in WSL2.

But I’m on wsl2 and windows 10.019041, ubuntu 20.04 and still have the problem. fuse: device not found, try ‘modprobe fuse’ first then when I modprobe fuse, I get modprobe: FATAL: Module fuse not found in directory /lib/modules/4.4.0-19041-Microsoft

can’t google any solutions to this. Is fuse still not supported on wsl2? Is so what is the roadmap for it?

@komali2 thanks for the heads up. I guess the owner of that link realized it was generating traffic and seized the oportunity or his hosting went down…

(Link edited out due to ad-hijacking) having support for it on Ubuntu on Windows would be pretty sweet !