Homelab

371 readers

9 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 11 months ago

MODERATORS

[email protected]

Moved all of my Docker instances hosted on LXC's over to VM's...it wasn't too horrible actually. (alien.top)

submitted 10 months ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I've been dreading doing it, however, it wasn't too bad. I had 4 LXC's to convert to VM's in total.

The biggest difference is that the LXC I had which hosted CodeProject.AI for my Blue Iris server went from using 120GB down to 19GB to for the same containers. I'm guessing it's due to being able to change from using vfs in the LXC to overlay2 in the VM.

Having docker-compose yml files to recreate all containers on the VM helped a TON as well as using rsync to move everything over to the new VM that the containers needed.

Has anyone else made the move?

I got the kick in the pants to do it after trying to restore the 120GB LXC from PBS, giving up after 2 hours, and restoring it in totality from a standard Proxmox backup instead which only took 15 minutes.

top 5 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 10 months ago

This is why I use locally mounted volumes for all my docker containers. Makes transferring over to new hosts an easy rsync one liner.

[–] [email protected] 1 points 10 months ago

I haven't dug into this too much, but I have seen mention of using overlay2 for lxcs on proxmox. If that was available would you still prefer VMs?

Here's one post I just found talking about the availability of it: https://forum.proxmox.com/threads/lxc-zfs-docker-overlay2-driver.122621/

[–] [email protected] 1 points 10 months ago

LPT: if you store your data on a NAS or somesuch, you can use NFS volumes to expose that data to your containers. That way, if you need to rejigger or blow away your setup, you don't lose anything that can't be rebuilt easily.

[–] [email protected] 1 points 10 months ago (1 children)

Did you see a performance improvement going from vfs to overlay2?

I'm still stuck on vfs as I don't want to mount my storage to the VM via NFS. Passing it into the lxc is so much more flexible and it doesn't come with the problems when dealing with database files.

[–] [email protected] 1 points 10 months ago

I can’t say that I’ve noticed anything, however, my containers aren’t IO intensive either.

I agree completely about the LXC being much more flexible when using bind mounts rather than fstab.