Trying to add an sshfs mounted location as a regular file system volume type in Cloudron

[makemrproper]

I meant Filesystem Volume type, yes. Will update original post to reflect this.

[makemrproper]

I will look into solving this at the hypervisor level and exposing folders to the guest vm that way.

[djxx]

I'm facing the same issue with Nextcloud and trying to tune the performance of SSHFS (https://forum.cloudron.io/topic/13852/sshfs-read-speed-significantly-slower-than-scp-with-the-same-target/9) . The answer, at least for Nextcloud, is to adjust the configuration file. Instead of trying to "trick" Cloudron into accepting an SSHFS mount point as the primary storage, just adjust the applications config file to point to the mount point. Not sure if it will work for Immich, but it works for Nextcloud.

Also, I'm doing this with Nextcloud for the exact same reason - I want to manage my pictures. I'm trying the "Memories" plugin in Nextcloud which has prettty good reviews. I'll probably move on to Immich next for testing.

[makemrproper]

Sounds like the case is identical, yes :).

Great workaround! I will try it.

Solving it at the hypervisor level is not any better than directly on the cloudron vm. There is no way to share a folder to a vm. Only nfs, cifs, sshfs or direct block device.

The reason is that our phones are growing, and at current I need to sync 5x family members phones at 1tb. Not insane anounts of course, but way beyond the m2.ssd cloudron is running on.

[robi]

@makemrproper said in Trying to add an sshfs mounted location as a regular file system volume type in Cloudron:

or direct block device

https://linbit.com/drbd/ is the gold standard.

[andreasdueren]

@makemrproper I'm sorry could you summarize or even give step-by-step instructions on what you ended up doing?

[joseph]

@makemrproper said in Trying to add an sshfs mounted location as a regular file system volume type in Cloudron:

When trying to I am trying to add the /mnt/folder to Cloudron as a filesystem volume type, I am getting this error: hostPath must be a realpath without symlinks

Just tested this and this works fine here. Is /mnt/folder a symlink? I have a fstab line to mount a sshfs into /mnt/folder . And then I just added Filesystem mount type in Volumes view.

[msbt]

Also getting that message, but on a different use-case. I'm trying to add a (sftp) rclone mount to Cloudron. Mounting and browsing works fine, but when trying to add it as a volume, it says hostPath must be a realpath without symlinks. Is that not supported?

[joseph]

Didn't get an answer to my earlier question. Is it a symlink? You can't add symlinks.

Can you try node -e "fs.realpathSync('/the/path')" ? This function is failing or returning something other than the path you are adding for some reason.

[msbt]

Can only speak for my issue, not a symlink:

/mnt# ls -la
total 12
drwxr-xr-x  4 root root 4096 Jun  9 09:21 .
drwxr-xr-x 23 root root 4096 Dec 17 11:10 ..
drwxr-xr-x  1 root root    0 Jun  9 09:22 media
drwxr-xr-x  2 root root 4096 Dec 17 11:31 volumes

Your command doesn't fail, but doesn't give any output either.

[joseph]

@msbt said in Trying to add an sshfs mounted location as a regular file system volume type in Cloudron:

Your command doesn't fail, but doesn't give any output either.

My bad... Can you try like this:

root@my:/mnt# node -e "console.log(fs.realpathSync('/mnt/folder'))"
/mnt/folder

[msbt]

@joseph sure:

/mnt# node -e "console.log(fs.realpathSync('/mnt/media'))"
/mnt/media

[joseph]

@msbt you are trying to add /mnt/media in the Volumes view ? I cannot see why https://git.cloudron.io/platform/box/-/blob/master/src/volumes.js?ref_type=heads#L57 will fail . That's where the error message comes from. If you are ok debugging a bit, just put some console.log in that function and systemctl restart box.

[msbt]

@joseph happy to, can you maybe enable chat so we can do that 1:1?

[joseph]

@msbt can you instead write to me at support@cloudron.io please? Will debug it right away.

[msbt]

My issue is resolved, adding a --allow-other parameter to the mount solved it, thanks @girish and @joseph