Docker install on synology nas

[oliv]

@karsten13 of course thanks for checking it out.

Here is the docker start command:

docker run  -d \
    --name magicmirror \
    --publish 8036:8080 \
    --restart unless-stopped \
    -e TZ=America/Chicago \
    --volume /volume1/docker/magicmirror/config:/opt/magic_mirror/config \
    --volume /volume1/docker/magicmirror/modules:/opt/magic_mirror/modules \
    --volume /volume1/docker/magicmirror/css:/opt/magic_mirror/css \
    karsten13/magicmirror:latest

and here are the logs of the container:

[karsten13]

@oliv

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.

[sdetweil]

@pauabaer typically the group id is the same as the user id

[sdetweil]

@pauabaer

id -u will get this users id number
id -g will get this users group number

[pauabaer]

@sdetweil
That’s what i checked before. Id -u > 1026 / id -g > 100.
These parameters i inserted in the compose file.

[pauabaer]

@karsten13

I tried to start via command line

paua@NAS:~$ docker run  -d \
>         --user root \
> --name magicmirror \
>     --publish 8036:8080 \
>     --restart unless-stopped \
>     -e TZ=Europe/Berlin \
>     --volume /volume2/docker/MagicMirror/config:/opt/magic_mirror/config \
>     --volume /volume2/docker/MagicMirror/modules:/opt/magic_mirror/modules \
>     --volume /volume2/docker/MagicMirror/css:/opt/magic_mirror/css \
>     karsten13/magicmirror:latest
docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=magicmirror": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.

But again I got the permission error.

[pauabaer]

I fixed it and now MM is running in docker on my synology diskstation.
I had to insert

user: root

in the compose file. It is working fine.