Folder share on additional disk

[lilian]

Hello everyone,

I have a small issue.

I’m on an OVH VPS with an additional disk mounted under /dev/sdc1 by cloudron.
I have some applications installed, and everything is working fine.

At the root of my additional disk, I created a folder named "media" that I want to share with some applications. I ran a chmod 777 -R media.

I added a new volume in Cloudron:

Mount type: filesystem
Local directory: /mnt/volumes/04067a3544294e0fa162392e066337cf/media
The status indicator is green, but when I click to explore the folder, it appears empty.

Is there a trick to get this shared folder to work properly?

[nebulon]

Assuming there are actually files in that folder....Do you see any errors in the browser console or the sftp service? (that is the one which offers the backend API for the filemanger)

[lilian]

Hi, thanks for your response.
I don't see any errors, and I even have a green light on the mount.
I don't understand why I don't have access to my folder. I tried changing ownership to Cloudron, but it didn't work.
There is a folder inside this folder, so yes, there is something inside.
Since I'm letting Cloudron manage the mount of the sdc1 disk, and this folder is at the root of this disk, could the problem be coming from there?
Attached are some screenshots.
Thanks.

[lilian]

Hi, I tried:

chmod a+rw /mnt/volumes/04067a3544294e0fa162392e066337cf/media

It didn't work.

I tried:

export MOUNT_DIR=/mnt/volumes/04067a3544294e0fa162392e066337cf/media
chmod 777 $MOUNT_DIR
hgrp media $MOUNT_DIR
chmod g+s $MOUNT_DIR
setfacl -d -m g::rwx $MOUNT_DIR
setfacl -d -m o::rx $MOUNT_DIR
touch $MOUNT_DIR/test-file
ls -l $MOUNT_DIR/test-file

Output:

-rw-rw-r-- 1 root media 0 Aug  7 15:53 /mnt/volumes/04067a3544294e0fa162392e066337cf/media/test-file

root@liello:/mnt/volumes/04067a3544294e0fa162392e066337cf/media# ls
partage  test-file
root@liello:/mnt/volumes/04067a3544294e0fa162392e066337cf/media#

It doesn't work. Is there something I did wrong? Thanks.

[joseph]

@lilian where did you get 04067a3544294e0fa162392e066337cf from ? The /mnt/volumes directory is managed by Cloudron and it's possible Cloudron is getting confused somewhere. May I suggest that you use some other directory like /srv/media instead?

[lilian]

Hi @joseph ,

If I create a folder in /srv/, I can access it from Cloudron (but that's not what I want to do since I want everything on the additional disk).

I have created the volume in Cloudron and added it to my Nextcloud (which is installed on the additional disk), but from within Nextcloud, I can't access the volume created in /srv/.

https://docs.cloudron.io/apps/#mounts

I think Cloudron is blocking all access! I find it strange that you can't share a folder across multiple applications.

What solutions are available?

[joseph]

@lilian I think you misunderstood what I said (or maybe I misunderstand your setup). I am asking you to mount your external/addition disk under /srv instead of under /mnt/volumes/04067a3544294e0fa162392e066337cf . Once you mount under /srv , you can then add it as a Volume with Filesystem or Mountprovider type. It was a bug that we allowed volumes to have host path under /mnt/volumes . This is fixed now for next release (https://git.cloudron.io/cloudron/box/-/commit/21705a0e966ef998e836e6b7fed0da00dadfee79)