Important – Do not blindly apply the commands here to containers or paths you have not set up via this site as you could unintentionally break other containers or even worse DSM as these commands are run as the Linux superuser (root)
When running through the guides on this site you may occasionally have permissions issues, before you just jump ahead and apply the commands read the following!!
Incorrect PUID or PGID (UID/GID)
The most common cause of permission issues is either not using the correct IDs or not entering them correctly so first check the following
- Use SSH to obtain the IDs just like in the Setting up a restricted user guide
- Check the numbers are the right way around such as PUID being in the PGID section.
- Are they the correct numbers – triple check them as often its a simple typo!
If you found an issue. Stop the container, update the IDs and start the container again.
Incorrect Paths
The guides have a set of paths that are consistent and make the overall setup clean and easy to understand if you have used these exactly then this won’t apply.
However, the second most common issue seen is trying to apply an existing shared folder setup to the guides. For example mapping an existing /Torrents and or /Movies folders to /data/movies etc.
I would recommend you stop at this point and take the time to migrate to a single overall shared folder as you are layering in complexity to your setup and just delaying future problems.
If neither of the above have applied move onto the commands
SSH Commands to update permissions
The permission fixes below perform two key actions
- Recursively makes the dockerlimited user and where required group, owners of all files and folders in the named paths
- Recursively changes file and folder permissions to 775 (rwxrwxr-x)
Ensure you use the correct ‘Command Set’ do not use both!
- Command Set 1 – For those who have the dockerlimited and dockergroup
- Command Set 2 – For those who only have the dockerlimited user in place
Command Set 1
Adjust the path /volume1/data to the exact path you are having issues with. I do not recommend applying this to the entire /data or /docker shared folders.
For example if you are having issues with torrents downloading (errored) then you would adjust the path to /volume1/data/torrents also ensure the volume reflects your actual volume number if you are using an SSD for docker it may be/volume2/docker/radarr for example.
You will not see any output after running each command, the first one will ask you to enter your main password.
sudo chown -R dockerlimited:dockergroup /volume1/dataThen once you have done the above use the next command also updating the path as per the first command.
sudo chmod -R a=,a+rX,u+w,g+w /volume1/dataYou should now be able to access the path used in your container, if not there is something else wrong in your setup, and you will need to reach out via Discord or the Comments for some help.
Command Set 2
Adjust the path /volume1/data to the exact path you are having issues with. I do not recommend applying this to the entire /data or /docker shared folders.
For example if you are having issues with torrents downloading (errored) then you would adjust the path to /volume1/data/torrents also ensure the volume reflects your actual volume number if you are using an SSD for docker it may be/volume2/docker/radarr for example.
You will not see any output after running each command, the first one will ask you to enter your main password.
sudo chown -R dockerlimited:users /volume1/dataThen once you have done the above use the next command also updating the path as per the first command.
sudo chmod -R a=,a+rX,u+w,g+w /volume1/dataYou should now be able to access the path used in your container, if not there is something else wrong in your setup, and you will need to reach out via Discord or the Comments for some help.
Be First to Comment