https://rancher.com/ logo
q

quick-keyboard-83126

11/30/2022, 9:05 PM
I have a container (neo4j) which runs w/ a user neo4j (101). I'm on macOS where my host user is 501:20. What do I need to do to get the inside container to see the files as owned by neo4j, but still allow the neo4j user to write to the files? If I change the owner on the macOS side to 101:101, then the rdshell side can't write to the files, and I think that's what causes the files not to be writable by neo4j even though neo4j has the 101 that matches the host side.
s

sticky-summer-13450

12/01/2022, 8:52 AM
Does
chmod 0666 *
help? i.e. ignore the owner just allow all users to read and write? I also tend to set the sticky-bit on the group for folders so that the group of the folder is inherited to the group of the files for new files that are created. i.e.
chmod 2777 .
on the root folder and all sub-folders of the folder you are sharing between systems.
q

quick-keyboard-83126

12/01/2022, 12:40 PM
I didn't try because I don't want to risk the database getting annoyed at me.
My guess is that it could be fixed by changing the sshfs magic.
8 Views