Docker install on synology nas

karsten13

looks like the volumes on the host were created by root. The user in the container runs as user node with uid/gid 1000.

So you can try

a) cd to /volume1/docker/ on the host and run chown -R 1000:1000 ./magicmirror (you have to do this as root)

or

b) run the container as user root, you have to add

    --user root \

to the docker run ... command

sdetweil

@karsten13 i think /opt is non existent on synology

karsten13

@sdetweil said in Docker install on synology nas:

@karsten13 i think /opt is non existent on synology

but in the container

sdetweil

this turned out to be a permissions problem. the folder was created w the synology user, but the container is running as user 1000

pauabaer

@karsten13

I have the same issue but I do not really know how to run the container as user node with uid/gid 1000.

You wrote two ways with the hint that this should happen as root. How do I do this?

And can I make this run just for the MagicMirror docker? Because I have other dockers with other uids/gids.

Thanks for your help.

Paua

sdetweil

@pauabaer just change the docker compose .env file userid number from 1000 to whatever it is on your synology nas ( mine is 1026)
(note the . in front of env)

sdetweil

@pauabaer yes, the user info is separate for each docker container

think of a docker container as a mini pc disc, memory, cpu and software all inside a little case (container shell)

pauabaer

@sdetweil
I tried it in the Synology gui. I have added puid and pgid as I did in other containers.

But I got the same message: access denied.

So what would be the difference when I change the entry whithin the compose?

And how do I find this file at my synology? :)

sdetweil

@pauabaer i do not know how to do it with the gui,
there is a place where you can paste in the compose file . i have not tried that

i ssh’d into the nas and did the manual install steps via commandline

pauabaer

@sdetweil
I startet the container with a compose file where I added the user 1026 and group ID 100 but there is no success.

Still the same error - see attached file.