Ancestors

Written by foremanguy on 2024-12-08 at 18:16

How to use LXC containers in Proxmox?

https://lemmy.ml/post/23362221

=> More informations about this toot | More toots from foremanguy92_@lemmy.ml

Written by walden on 2024-12-08 at 18:56

If I remember correctly, Proxmox recommends running Docker in virtual machines instead of LXC containers. I sort of gave up on LXC containers for what I do, which is run stuff in Docker and use my server as a NAS with ZFS storage.

LXC containers are unprivileged by default, so the user IDs don’t match the conventional pattern (1000 is the main user, etc.). For a file sharing system this was a pain in the butt, because ever file ended up being owned by crazy user. There are ways around it which I did for some time, but moving to virtual machines instead has been super smooth.

They also don’t recommend running Docker on bare metal (Proxmox is Debian, after all). I don’t know the reasons why, but I tend to agree simply for backups. My Docker VMs get automatically backed up on a schedule, and those backups automatically get sent to Backblaze B2 on a schedule

=> More informations about this toot | More toots from walden@sub.wetshaving.social

Toot

Written by foremanguy on 2024-12-08 at 19:11

Basically I want to get rid of docker for the most part, and run apps directly into containers. So if one of my services corrupt or something bad happen I can recover from backup without affecting others. So how do you apply your backups when running several services in docker?

=> More informations about this toot | More toots from foremanguy92_@lemmy.ml

Descendants

Written by Oisteink@lemmy.world on 2024-12-08 at 19:44

There are big differences between these two technologies. LXC is closer to a virtual machine than a docker setup. You could mimic most of a dockerfile if you wanted, but it’s not a replacement.

Most of us will use a mix og docker-hosts(vm’s running docker) and lxc. Reasons for this is that some stuff is easier to maintain in docker as it’s the preferred release channel.

You can also move vm’s to other datacenter hosts if needed - and with shared storage this is quick and mean no downtime. Lxc are stuck on the host.

=> More informations about this toot | More toots from Oisteink@lemmy.world

Written by Oisteink@lemmy.world on 2024-12-08 at 19:48

Backup of docker would either be full host - for a simple and inflexible setup, or you do data and config backup (volumes mounted in docker), and rely on docker rebuilding the images.

=> More informations about this toot | More toots from Oisteink@lemmy.world

Written by notfromhere@lemmy.ml on 2024-12-09 at 04:58

Honestly, what you’re trying to do is a great use case for docker already. I suggest learning more about how to use docker, take backups, restore from backups, etc. E.g., I have a NFSv4 share that I store all of my containerized services’ config and data files in. Any time I need to restore a precious version, it’s as easy as restoring the previous version files and starting the previous version container.

=> More informations about this toot | More toots from notfromhere@lemmy.ml

Written by foremanguy on 2024-12-09 at 07:01

Yeah that could be an option too, but I kinda like the way how lxc works so I’m going to stick to it and write scripts to make the whole thing automated

=> More informations about this toot | More toots from foremanguy92_@lemmy.ml

Written by notfromhere@lemmy.ml on 2024-12-09 at 14:28

Check out ansible for ways to automate this stuff. Highly recommended!

=> More informations about this toot | More toots from notfromhere@lemmy.ml

Written by foremanguy on 2024-12-09 at 17:08

I thought to only cron to run weekly update

=> More informations about this toot | More toots from foremanguy92_@lemmy.ml