I’ll start. Did you know you can run a headless version of JD2 on a raspberry pi? It’s not the greatest thing in the world, but sometimes its nice to throw a bunch of links in there and go to sleep.

  • @Shere_Khan@lemmy.dbzer0.comOP
    link
    fedilink
    English
    51 year ago

    I’m just now dipping my toes into docker. I started off self hosting a bitwarden server, and im working on moving my *arrs over to containers on my nas. I need a bit more experience before i move my seedbox over fully, dont need any more isp letters.

    I had no idea about those apps, thats sick dude

    • eroc1990
      link
      fedilink
      English
      41 year ago

      I used to run the applications on bare metal when I ran a Windows server (because that’s all I knew at the time). Eventually graduated to a QNAP NAS, that wasn’t enough, and moved on again to Unraid, where many of these apps are available through templates in their Community Apps section. It really lowers the barrier of entry for using Docker and makes it stupid easy to assign your container an IP address on your host network, so it can be its own “device” on your LAN (which helps for me since I’ve got that all segmented off in its own VLAN).

      It’s not too deep a rabbit hole to jump down, but it’ll take time to get things just right to limit the amount you need to interact with the apps and manually select what you want to grab.

      • @Shere_Khan@lemmy.dbzer0.comOP
        link
        fedilink
        English
        3
        edit-2
        1 year ago

        Yeah im just about there. Eventually i want to build my own nas, but i got a pretty solid synology for cheap and it is good enough for plex and all the docker containers so far.

        you are spot on about lowering the barrier of entry tho. I remember trying to set up programs to auto run on boot on a raspberry pi lol, now all i do is double click an icon and supply my ports. crazy easy

        • eroc1990
          link
          fedilink
          English
          11 year ago

          Nothing wrong with using what you’ve got and upgrading. And the beautiful thing about Docker is you can just spin up the container elsewhere, point the mount points to their new locations, make sure your perms are good, and continue like nothing changed.

          It really is so much easier now. And with UnRAID acting as my container host, it saves everything I spin up (permanent or not) in its last state as a template, so if I need to destroy my docker image disk (which I recently ran into) all I need to do is find the template I was using from the dropdown they give you and click Create. Not a backup solution (which you should also have), but it’s such a time saver if and when something goes horribly wrong, or if you want to spin a container you used to use but since destroyed back up.

          • @Shere_Khan@lemmy.dbzer0.comOP
            link
            fedilink
            English
            21 year ago

            when something goes horribly wrong,

            I like how thats not IF, lol. I swear dude, i have so many sd card images ready for when i inevitably mess something up.

            Do you use a server rack for your nas? or just an old pc case?

            • eroc1990
              link
              fedilink
              English
              21 year ago

              100% when. I’ve learned that the hard way too many times to count at this point…

              My NAS is built into an (I think) Thermaltake mid-sized tower running consumer hardware (ASRock X570 Phantom Gaming 4, Ryzen 5 series G proc, G.Skill non-ecc RAM) with the exception of one hard drive. Both that and my proxmox host are repurposed or custom built towers.

              I do still use the QNAP NAS too, though only as SMB for my desktop/NFS for my server.

    • operator
      link
      fedilink
      31 year ago

      Make sure you have backups of your vault. Reliable backups.

      Especially if you are just starting off with docker, you don’t want to loose access to all your accounts because you f up some configuration (e.g. redeploy an updated image)