Closed Moonpengu closed 6 months ago
I don't really see how this is a fireshare issue however make sure you are setting the PUID and PGID values to a user that has read/write access to your networked mount point. That is really the best guess I have as to why you are seeing a permission denied.
You can test this by simply creating a temporary network mount point that is read/write to all users and point that at fireshare and see if it works.
One other thing I noticed that could be the problem is an issue in your docker-compose config. You seem to have changed the volume maps that fireshare needs which might be making it so that it can't find the expected folders.
This is how your config should be. do not change the paths on the right side of the color. Those are the maps to the folders within the fireshare container and must not be changed. You will also need to have separate folders within your mount point for each (data, processed, videos).
volumes:
- fireshare-data/data/:/data
- fireshare-data/processed/:/processed
- fireshare-data/videos/:/videos
Try updating your config to that and then restarting then recreating the fireshare docker container.
I don't really see how this is a fireshare issue
Sorry, you're right. I need to get more sleep, I spent way too long going round in circles overlooking the obvious.
Thanks for the help regardless.
I'm having some permissions issues when trying to set my videos directory to a networked drive using CIFS.
This occurs when using a mounted directory on the host using bind and using a networked volume using CIFS. None of the files that are meant to be created there are created as permissions seem to be insufficient. When checking the videos folder doesn't appear to get created as the nginx user, so I attempted to give it ownership, but that doesn't seem to work.
There are no problems when using a local volume or bind directory. I did some digging to see what I was doing wrong, but I can't seem to figure this one out.
Any clues?
To Reproduce Steps to reproduce the behavior:
Expected behavior Networked storage should behave the same as local storage
Additional context
The following permissions error is observed on startup and whenever access to videos is attempted:
I'm using the following docker compose:
and the volume is configured as seen here: