20
HomeServer main storage upgrade
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Sep 2023
20 points (91.7% liked)
Selfhosted
40246 readers
822 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
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.
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.
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?
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.
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.