Rclone (vfs) mounts using autofs and rclonevfs not visible in nautilus nor bindable in docker container

What is the problem you are having with rclone?

mounts using autofs and the rclonefs script (cf rclone mount helper script · rclone/rclone Wiki · GitHub) do not behave like the usual standard rclone mounts.
autofs rclone mounts:

  • not visible in nautilus: no "volume" listed on left panel
  • nautilus can not list files even if started with the folder as argument: keeps spinning

but usual rclone mounts (S3, ftp, ...) :

  • are visible in nautilus (gnome file explorer)

Just wanted to check if it is expected, or if there is some option to control that behaviour.
I guess that it is probably due to autofs, but I'm looking for any feedback to help me understand the problem.
N.B: will post detailed setup shortly

What is your rclone version (output from rclone version)


Which OS you are using and how many bits (eg Windows 7, 64 bit)

Which cloud storage system are you using? (eg Google Drive)

S3, ftp

  • first make sure you can access the rclone mount on the command line.
  • did you add --allow-other to the rclone mount command?

if that does not solve the problem, then
start a new topic, using the help and support template, and answer all the questoins.

ah I forgot an important detail: it's when mounting with autofs/automount. Let me correct the post...

cf Ls on autofs triggered rclone mount hangs the first time

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.