MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Docker install on synology nas

    Scheduled Pinned Locked Moved Solved Troubleshooting
    18 Posts 4 Posters 2.3k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • karsten13K Offline
      karsten13 @oliv
      last edited by

      @oliv

      to understand what is happening I need

      • the full logs of the container
      • the start command (full docker run ... or compose file)
      1 Reply Last reply Reply Quote 0
      • O Offline
        oliv
        last edited by

        @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:
        Screenshot 2024-09-04 at 11.32.22 AM.png

        karsten13K 1 Reply Last reply Reply Quote 1
        • karsten13K Offline
          karsten13 @oliv
          last edited by

          @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

          S P 3 Replies Last reply Reply Quote 1
          • S sdetweil referenced this topic on
          • S Offline
            sdetweil @karsten13
            last edited by

            @karsten13 i think /opt is non existent on synology

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            karsten13K 1 Reply Last reply Reply Quote 0
            • karsten13K Offline
              karsten13 @sdetweil
              last edited by

              @sdetweil said in Docker install on synology nas:

              @karsten13 i think /opt is non existent on synology

              but in the container

              1 Reply Last reply Reply Quote 0
              • S Offline
                sdetweil @oliv
                last edited by 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

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 1
                • S sdetweil has marked this topic as solved on
                • P Offline
                  pauabaer @karsten13
                  last edited by

                  @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

                  S 2 Replies Last reply Reply Quote 0
                  • S Offline
                    sdetweil @pauabaer
                    last edited by

                    @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)

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    P 1 Reply Last reply Reply Quote 0
                    • S Offline
                      sdetweil @pauabaer
                      last edited by

                      @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)

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

                      1 Reply Last reply Reply Quote 0
                      • P Offline
                        pauabaer @sdetweil
                        last edited by

                        @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? :)

                        S 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 1 / 2
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy