Hello selfhosters!

I’v small homeServer (Dell Wyse 5070) and I’m thinking about upgrade of main SSD M.2 storage.

Currently most of my services are docker containers. During upgrade I want to refresh whole setup and learn ansible a bit during the process.

I’ve got few services that I want to avoid to stop for hours/days which could take me to set the whole server from scratch in the new way (NextCloud, Home Assistant, Matrix), all of them used locally (trough Tailscale) by my family.

I’m thinkging about keeping them running, by connecting old SSD M.2 drive to my laptop and run inside VM. Do you think that will be doable / what kind of troubles I can get through that process? Asking about that “keeping services on my laptop” think. With refresh of server it will of course be the journey with troubles, but I will have time for that, when crucial services will be running on different machine.

  • @thirdBreakfast@lemmy.world
    link
    fedilink
    English
    31 year ago

    Sounds like it would be easier to run your VM on the laptop, leave the SSD in the 5070, and move each service over to the laptop one at a time. Then nuke and repave the 5070 with the upgraded drive, and then move the services back.

    Ansible is great, but I’d leave learning that as a separate project in the future. Convert to docker compose as part of this process if you’re not already doing that.

    • @arkhos@lemmy.mlOP
      link
      fedilink
      English
      11 year ago

      Moving services one by one could be a solution but required additional networking - currently I’ve got Tailscale domains for mentioned critical ones (Nextcloud, Matrix) and I thought about running from the same storage could keep the same hostnames of Tailscale nodes (if that even possible). What do you think about that issue?

      Currently I’ve got all of the docker containers defined troguht Portainer Stacks, so I could easily covert it to base docker compose files.

      • @thirdBreakfast@lemmy.world
        link
        fedilink
        English
        11 year ago

        I’m not clear on how your tailscale names are attached to the services. Do you mean you’ve got a different Tailscale magic DNS for each docker container with a sidecar?

        I’m not a Tailscale expert, all my services are in VM’s or LXC’s so they get their own Tailscale name that moves with them. Perhaps Tailscale allows you to add extra names for the same host or something?

        • @arkhos@lemmy.mlOP
          link
          fedilink
          English
          11 year ago

          I’ve got few docker containered Tailscale deamons as a sidecar, exactly. Those should work as the same host (login based), as in the original home server. I’m mostly unsure, how the whole “VM environment” with attached drive with whole docker engine install will perform - also in terms of connection.

          • @thirdBreakfast@lemmy.world
            link
            fedilink
            English
            21 year ago

            So their names would come across with them. In what I’m proposing, you wouldn’t worry about attaching the drive. Just copy the data for one service over, then start it’s container on the laptop. Once that’s all working fine, do the rest one at a time till they’re all on the laptop. Then wipe your Dell and start from scratch.