From 14081275d16e99494534bf5135e3a12fc18280d9 Mon Sep 17 00:00:00 2001 From: TRaSH Date: Sun, 24 Jan 2021 10:02:59 +0100 Subject: [PATCH] Update how-to-set-up-hardlinks-and-atomic-moves.md - Added: added extra note for Synology permissions. --- .../how-to-set-up-hardlinks-and-atomic-moves.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/Misc/how-to-set-up-hardlinks-and-atomic-moves.md b/docs/Misc/how-to-set-up-hardlinks-and-atomic-moves.md index 0c1880d4c..40bd55839 100644 --- a/docs/Misc/how-to-set-up-hardlinks-and-atomic-moves.md +++ b/docs/Misc/how-to-set-up-hardlinks-and-atomic-moves.md @@ -527,6 +527,21 @@ Then keep reading. sudo chmod -R a=,a+rX,u+w,g+w /volume1/data /volume1/docker ``` + !!! note + Synology doesn't always pick up the `$USER` correctly, you can test it if the right user is been used with the following command + + ```bash + ls -al /volume1/docker + ``` + + and user should be the same user you used for your PUID ! + + If it isn't the same then you need to replace `$USER` with the user what you used for your PUID, in the following example I used admin like we did in the start of the guide. + + ```bash + sudo chown -R admin:users /volume1/data /volume1/docker + ``` + ##### Run the Docker Compose !!! important