How do I make a volume mounted using sudo sshfs visible without sudo? After upgrading my Mac to macOS Sierra (10.12.5), I upgraded FUSE for macOS (https://osxfuse.github.io) to the latest stable releases: FUSE for macOS 3.6.3 and SSHFS 2.5.0.

But now this no longer works:

$ sudo mkdir -p /Volumes/ssh_fs_5810 &amp;&amp; sshfs dspitzer@dspitzer-5810:/home/CORP/dspitzer /Volumes/ssh_fs_5810/
mount_osxfuse: failed to mount /Volumes/ssh_fs_5810@/dev/osxfuse0: Operation not permitted


/Volumes/ssh_fs_5810 exists:

$ ls /Volumes
Macintosh HD ssh_fs_5810


Apparently sshfs now requires sudo:

$ sudo sshfs dspitzer@dspitzer-5810:/home/CORP/dspitzer /Volumes/ssh_fs_5810/
dspitzer@dspitzer-5810's password:


But now /Volumes/ssh_fs_5810/ is not visible without sudo:

$ ls /Volumes
ls: ssh_fs_5810: No such file or directory
Macintosh HD
$ sudo ls /Volumes
Macintosh HD    ssh_fs_5810
$ sudo ls /Volumes/ssh_fs_5810
.ICEauthority           .ssh
...


How do I make /Volumes/ssh_fs_5810/ (the directory I mount into using sudo sshfs) visible without sudo?

Update (addressing SteppingHat's comment):

Yes, the owner of /Volumes/ssh_fs_5810/ is root:

$ sudo ls -l /Volumes
Password:
total 16
lrwxr-xr-x  1 root      wheel     1 Aug 22 16:09 Macintosh HD -&gt; /
drwxr-xr-x@ 1 root      wheel  4096 Aug 22 16:06 ssh_fs_5810


But this doesn't work:

$ sudo chown dspitzer:admin /Volumes/ssh_fs_5810/
chown: /Volumes/ssh_fs_5810/: Operation not permitted


And note above, /Volumes/ssh_fs_5810/ is visible after I create it using sudo, but not after sudo sshfs:

$ sudo umount -f /Volumes/ssh_fs_5810
$ sudo ls -l /Volumes
total 8
lrwxr-xr-x  1 root      wheel    1 Aug 22 16:09 Macintosh HD -&gt; /
$ sudo mkdir /Volumes/ssh_fs_5810/
$ sudo ls -l /Volumes
total 8
lrwxr-xr-x  1 root      wheel    1 Aug 22 16:09 Macintosh HD -&gt; /
drwxr-xr-x+ 2 root      wheel   68 Aug 22 18:05 ssh_fs_5810
$ ls /Volumes
Macintosh HD sh_fs_5810


Update #2 (in response to klanomath's "I've tested my alternative proposal..." comment on his answer below):

Here's what happened when I tried klanomath's alternative proposal:

$ ls /Volumes
Macintosh HD
$ sudo mkdir -p /Volumes/ssh_fs_5810
$ ls /Volumes
Macintosh HD ssh_fs_5810
$ sudo sshfs dspitzer@dspitzer-5810:/home/CORP/dspitzer /Volumes/ssh_fs_5810/
dspitzer@dspitzer-5810's password:
$ ls /Volumes
ls: ssh_fs_5810: No such file or directory
Macintosh HD
$ sudo chown dspitzer:admin /Volumes/ssh_fs_5810/
chown: /Volumes/ssh_fs_5810/: Operation not permitted
$ ls /Volumes
ls: ssh_fs_5810: No such file or directory
Macintosh HD
$ sudo ls /Volumes
Macintosh HD    ssh_fs_5810
Create a mount point in your user's realm and mount it there:

mkdir -p ~/Shares/ssh_fs_5810 &amp;&amp; sshfs dspitzer@dspitzer-5810:/home/CORP/dspitzer ~/Shares/ssh_fs_5810/




As an alternative you can add a sudo chown command after creating the mount point in your example (mounting to a subfolder of /Volumes):

... &amp;&amp; sudo chown %user%:%group% /Volumes/ssh_fs_5810 ...


with %user%: dspitzer and %group%: staff (or admin - depends on your user privs).

The total command is then:

sudo mkdir -p /Volumes/ssh_fs_5810 &amp;&amp; sudo chown dspitzer:admin /Volumes/ssh_fs_5810 &amp;&amp; sshfs dspitzer@dspitzer-5810:/home/CORP/dspitzer /Volumes/ssh_fs_5810


Running this command for the very first time seems to be rocky sometimes. Connecting to the remote host via ssh first (to add the remote host to the known_hosts file) and/or adding two times sleep 0.5 in between may help.