Issue seeing contents of directory after migrating to new Synology NAS

[juan9999]

Hi, I migrated to a new Synology NAS and using the same yaml and a backup of my config file that was working fine for me previously.

I am no longer able to see my subdirectories/files within crashplan (manage files), but if I SSH into the container (as root) then all the subdirectories and files appear fine. I've currently out of ideas and would appreciate some help.

I've tried the following but none seem to have worked for me:

• setting the PGID and PUID of my main user
• Removing the PGID and PUID
• Mapping the volume to the volume1 (what I originally had)
• Mapping the volume to shared folders (because I read you can't map to volume1 on synology although this has worked for me on my old server for a long time

Thanks in advance!

version: '3'
services:
crashplan-pro:
hostname: docker-crashplan-xpe1
image: jlesage/crashplan-pro:latest
restart: unless-stopped
environment:
- CRASHPLAN_SRV_MAX_MEM=10240M
- PGID=100
- PUID=1026
- TZ=America/Chicago
- KEEP_APP_RUNNING=1
ports:
- 5800:5800
volumes:
- /volume1/docker/crashplan-pro:/config:rw
- /volume1/shared:/shared:ro
- /volume1/media:/media:ro

[jlesage]

PUID and PGID are not used by the container. You must use USER_ID and GROUP_ID.
See https://github.com/jlesage/docker-crashplan-pro#environment-variables

[juan9999]

Thanks so much for the tip!

I changed it but it still doesn't resolve my issue :/

Still when I ssh into container, I see all the subfolders/files (can't write- so the ro is working), but when I press manage files in the gui, I can see the root of the shares, but nothing underneath.

[jlesage]

It should be a permission issue...

Do you see that permission/ownership of folder/files are correct?

docker exec <container name> ls -ld /media
docker exec <container name> ls -l /media/

[juan9999]

yeah, I just can't figure out how to fix.

I've verified that the owner in synology has the correct USER_ID and GROUP_ID.

here is a screenshot of rights in synology:

here is one from within the console in portainer

here is my .yaml

thanks again for your help!

[jlesage]

So from inside the container, we see that folders have no permissions (d---------).

I'm not sure to know what is causing this... Do you have the same behaviour if you create the container from the Container Station or from the CLI ?

[jlesage]

Also, could you share the full config of the container by providing the output of docker inspect <container name> ?

[juan9999]

thanks for bearing with me.

to answer your questions, my NAS had a volume corruption so I had to rebuild it and upgraded DSM versions and docker compose while I was at it, and I decided to migrate everything to .yaml and portainer, so not everything is 1:1.

attached is the output of the command that you requested after using the yaml. It's interesting that these variables aren't what I entered
"USER_ID=1000",
"GROUP_ID=1000",

I tried my old docker command WITH a mapping of the root of volume1 and it worked! I modified the original command to run with USER_ID and GROUP_ID vs PGID and PUID but the inspect also showed same as above (1000). Note default admin user is disabled in DSM. Also, the container did not appear on the synloogy docker app and doing the ls -l as above showed the same rights, but it was visible within the crashplan app under manage files! I don't get it!

To double check that it wasn't just mapping the root volume to storage that changed things, I deleted the container and reran the compose file above but changing the volume mapping to be the same as in the above syntax and it did NOT work.

Also, I ran the CLI and changed the mapping to subfolders and it did not work.

The only other thing that's weird is the the rights on docker/config/crashplan-pro the owner is part of the adminstrators group and not user group as in posts above

I don't get it.

I still haven't run a backup so not 100% sure it's fixed, but so far with the docker command line, I'm at least able to see the directories.

here is the output of the inspect (using docker compose) output is same via command line (at least for user id etc)

[JoshClose]

I was having this issue also and this fixed it for me! I think the fix specifically for me was setting USER_ID=<admin> and GROUP_ID=<administrators>