• sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    I haven’t used Synology, so I’m not sure. So I’ll just explain a bit how Docker works, which will hopefully give some context.

    Terminology:

    • image - the stuff hosted on https://hub.docker.com - basically the application and any dependencies it has
    • container - a disposable runtime for an image; stores new files separately from the image

    By default, the container doesn’t have access to anything that’s not explicitly passed to it, kind of like a VM, but without the expensive overhead a VM has.

    So the issues could be:

    • the image is incompatible with the host - pretty rare, but it happens
    • the container isn’t started
    • the container doesn’t have what it needs - maybe you need to expose a network port, or pass it a file
    • the Synology application isn’t configured to use the container

    For Synology and RustDesk specifically, I found this in the instructions:

    Synology has two types of Docker, “Docker” and “Container Manager”. If you’re using DSM 7.2 and later, please follow the guide for DSM 7.2, or follow the DSM 6 guide if you’re on older system.

    • Synology DSM 7.2
    • Synology DSM 6

    If you are using Synology with Portainer, please check this tutorial.

    If I had a Synology system to test with, I’d look into it for you, but that’s the best I’ve got. I run my own DIY NAS (old PC running openSUSE Leap w/ BTRFS, Samba, and minidlna configured).

    • LucidNightmare@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      The other user on this thread pointed out, as you have, that they’ve updated the guide to include DSM 7s Container Manager, which is what I was originally trying it on to begin with. So, thanks to both of you, I now have a project to do this weekend to test out the updated guides! :)