• mrnobody@reddthat.com
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    9
    ·
    3 months ago

    I’m going against the new-age tech grain with this, but… I fucking despise docker anything. I can follow directions fine, it’s the troubleshooting that takes too much time. Sure, I’ll learn it eventually, but I do IT for a living I’m not coming home to waste my nights also doing this.

    I’ve setup ZimaOS as a massive NAS with Yunohost on anything web-hosted/accessible. A. It’s easier with a graphical UI on stuff that’s packaged. B. Installing, updating, and most other services are pretty well automated/packaged to work really well. C. When i have the conversations with friends who aren’t tech savvy and are overwhelmed, I want to have firsthand knowledge of easy systems that’re basic, but powerful, and will help them dip their toes in freedom.

    No Proxmox, unraid, no docker stuff, no nested VMs, no more complex setups. While I can learn to troubleshoot and memorize CLI, I’m too old and busy with family and work/commute to deal with problems at home lol. Too much tinkering has poised my wife off to the point she thinks all the self hosted stuff is unreliable. So, I deploy, test, vet basic issues, and if it’s too much time or setup involved, or dependencies on other apps, I’m out!!

    Too many containers, too many fragile, partial service apps that just feel incomplete. Yuno and Zima (formerly casa) are great!! Others being tested too for fun but at snails pace lol.

    • x00z@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 months ago

      I had that same feeling until I actually learned it.

      There’s close to no performance loss, it’s better for security, it makes it extremely easy for developers to ship something that just works, it allows easy updating, and much more.

      I prefer docker over almost anything now, and it has made my life much easier.

      • osanna@lemmy.vg
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        my SD card in my ras pi got corrupted recently. Thankfully I had my docker directory backed up. I pulled the docker directory, docker compose up -d and within about 20 minutes (not including downloading time) I was back up and running. Docker is a godsend. all my apps were exactly as they were before the corruption.

        • x00z@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          Not sure how your docker directory and services look like but the important thing is that you use remote volumes (or backed up ones) and that you backup your compose file and mounted config files of course. But besides that it’s indeed that easy.

    • Imaginary_Stand4909@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      I still don’t truly know how to use docker, as I use dockSTARTer on my Debian VM on Proxmox, but it runns all my services now. I tried to resist and have multiple LXCs run everything, but as my homelab grew more complex (SMB & NFS, VPN tunnels, filesharing/hardlinks, etc.) I’ve just given up and have most things running on the docker. With dockstarter it’s enter “yes” to some terminal qs, copypaste templates into your overrides folder, and then use ds -u for update and ds -c to run everything.

      I tried to use podman at first because people said it was safer and faster but… I literally couldn’t figure out how to turn a pod into a service so it will autostart on system launch 😅