• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Using Synology Surveillance Station and Docker

    Support
    3
    19
    1760
    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.
    • Monocle
      Monocle @burkminipup last edited by

      @burkminipup

      Here is where my docker compose file exists.

      04578304-79f2-415f-b719-917d5397ca73-image.png

      Its in the same “monocle” shared folder located on “Volume 1” as my monocle.token file.

      Monocle: https://monoclecam.com
      Getting Started | Troubleshooting Guide | FAQ | Contact Support

      B 1 Reply Last reply Reply Quote 0
      • B
        burkminipup last edited by

        After about the 5th time, I got it created with this syntax:

        docker network create -d macvlan --subnet=192.168.0.0/24 --gateway=192.168.0.1 -o parent=bond0 monocle-network

        Now do I need to upload the .yml file separately? I have already assigned it through GUI.

        Monocle-Network.PNG

        Monocle 1 Reply Last reply Reply Quote 0
        • B
          burkminipup @Monocle last edited by

          @Monocle

          I could not get Monocle to use that directory for my token. I will just put the .yml in the same directory that my token is currently working in.

          Monocle 4 Replies Last reply Reply Quote 0
          • Monocle
            Monocle @burkminipup last edited by

            @burkminipup

            I just copied the docker-compose.yml file to my “monocle” shared folder, then from the command line I used the docker-compose tool with the -up argument. Something like this:

            docker-compose up -d ./docker-compose.yml
            

            see: https://docs.docker.com/compose/reference/up/

            Monocle: https://monoclecam.com
            Getting Started | Troubleshooting Guide | FAQ | Contact Support

            1 Reply Last reply Reply Quote 0
            • Monocle
              Monocle @burkminipup last edited by

              @burkminipup

              The docker-compose will auto create the container and network stack, you should not have to manually create the macvlan network.

              Monocle: https://monoclecam.com
              Getting Started | Troubleshooting Guide | FAQ | Contact Support

              1 Reply Last reply Reply Quote 0
              • Monocle
                Monocle @burkminipup last edited by

                @burkminipup

                I’m not sure this is correct in your docker-compose yml.

                    volumes:
                          - /etc/monocle:/etc/monocle:/docker/etc/monocle
                

                Mine is:

                • /volume1/monocle:/etc/monocle

                This means /volume1/monocle on the NAS gets mounted as /etc/monocle inside the running container.
                This allows us to store the monocle.token file and any other config outside of the container and allow you to stop and start/destroy/rebuild your container without losing any config.

                Monocle: https://monoclecam.com
                Getting Started | Troubleshooting Guide | FAQ | Contact Support

                1 Reply Last reply Reply Quote 0
                • Monocle
                  Monocle @burkminipup last edited by Monocle

                  @burkminipup

                  FYI, I am logged in via SSH using an “admin” level access account on the NAS.

                  Monocle: https://monoclecam.com
                  Getting Started | Troubleshooting Guide | FAQ | Contact Support

                  1 Reply Last reply Reply Quote 0
                  • Monocle
                    Monocle @burkminipup last edited by

                    @burkminipup said in Using Synology Surveillance Station and Docker:

                    I could not get Monocle to use that directory for my token. I will just put the .yml in the same directory that my token is currently working in.

                    I don’t think it matters where “docker-compose.yml” exists. Monocle-Gateway does not use this file. So no need for it inside the container.
                    You can put it anywhere on your NAS so long as you can access it via the SSH terminal to your NAS. Then just use the docker-compose executable to load this docker-compose.yml config file. This will make Docker build the container and networking stack.

                    Monocle: https://monoclecam.com
                    Getting Started | Troubleshooting Guide | FAQ | Contact Support

                    1 Reply Last reply Reply Quote 0
                    • B
                      burkminipup @Monocle last edited by

                      @Monocle

                      When you said:

                      • ipv4_address is the STATIC IP address I want to manually assign to the gateway. (Note: this address should be reserved or outside the DHCP range of your network router.)

                      Are you creating an IP address for the gateway? I have my IP address outside my DHCP pool, but I want to confirm that this is not supposed to be the NAS IP address. I have the gateway of the macvlan set to my router.

                      Another thing, would port-forwarding help allow my streams to make a connection? I can get the Monocle RTSP server running, but have not had luck with the connection. Also, after the connection fails, then Monocle goes into a disconnect loop.

                      Monocle-Network Disconnect.JPG

                      I am going to also try with a non Synology RTSP setup when I get home.

                      Thanks again.

                      Monocle 1 Reply Last reply Reply Quote 0
                      • Monocle
                        Monocle @burkminipup last edited by

                        @burkminipup said in Using Synology Surveillance Station and Docker:

                        @Monocle
                        When you said:

                        ipv4_address is the STATIC IP address I want to manually assign to the gateway. (Note: this address should be reserved or outside the DHCP range of your network router.)

                        Are you creating an IP addres

                        It’s an IP address that gets assigned to the Monocle Gateway instance running as a Docker container. Its an IP address that is valid on your existing private LAN, but one that is outside your DHCP range so that you don’t end up with two nodes on the network competing for the same address.

                        The errors you posted are acting like the Monocle Gateway cannot access the Internet or possibly does not have a valid DNS server to resolve the hostname for the Monocle API server.

                        I don’t think any port forwarding is required.

                        I am going to also try with a non Synology RTSP setup when I get home.

                        I agree, lets get it working here first before complicating the setup with a Docker container running on the Synology.

                        Thanks, Robert

                        Monocle: https://monoclecam.com
                        Getting Started | Troubleshooting Guide | FAQ | Contact Support

                        Monocle 1 Reply Last reply Reply Quote 0
                        • Monocle
                          Monocle @Monocle last edited by

                          How To Install Monocle Gateway on a Synology NAS as a Docker Container

                          How To Install Monocle Gateway on a Synology NAS as a Docker Container
                          Article:
                          https://monoclecam.com/monocle-gateway/install/synology

                          Monocle: https://monoclecam.com
                          Getting Started | Troubleshooting Guide | FAQ | Contact Support

                          1 Reply Last reply Reply Quote 0
                          • V
                            Velocity last edited by Velocity

                            I am also experiencing a similar issue, I set the docker instance up without any issues. However my echo show keeps saying “the camera isn’t responding”.

                            I have pasted a copy of my log to the link below, any assistance would be appreciated:
                            https://pastebin.com/MhCxf8bj

                            Here is my camera feed history:

                            [
                              {
                                "timestamp": "2019-12-04T17:59:41.976Z",
                                "request": "InitializeCameraStreams",
                                "response": [
                                  {
                                    "uri": "rtsp://%USER%:%PWD%@192.168.0.40:554/Sms=2.unicast",
                                    "proxy": "rtsp://87939317-d807-451b-8275-24ce48c5e5b8.mproxy.io:443/STREAM:fabda600-c841-4e0e-ab69-aff675d202ff?session=8842c12c-3a24-4061-a604-85428d243a73",
                                    "resolution": {
                                      "width": "1920",
                                      "height": "1080"
                                    },
                                    "authorizationType": "DIGEST",
                                    "videoCodec": "H264",
                                    "audioCodec": "AAC",
                                    "protocol": "RTSP"
                                  }
                                ]
                              }
                            

                            And finally a screenshot of my cam setup in the Monocle portal:
                            Screenshot 2019-12-04 at 18.01.48.png

                            Thanks,
                            Vel

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Privacy Policy  |  Terms & Conditions

                            © 2018 shadeBlue, LLC.