this post was submitted on 20 Feb 2025
37 points (95.1% liked)

Selfhosted

42714 readers
319 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I run a small server with Proxmox, and I'm wondering what are your opinions on running Docker in separate LXC containers vs. running a specific VM for all Docker containers?

I started with LXC containers because I was more familiar with installing services the classic Linux way. I later added a VM specifically for running Docker containers. I'm thinking if I should continue this strategy and just add some more resources to the docker VM.

On one hand, backups seem to be easier with individual LXCs (I've had situations where I tried to update a Docker container but the new container broke the existing configuration and found it easiest just to restore the entire VM from backup). On the otherhand, it seems like more overhead to install Docker in each individual LXC.

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 2 points 2 days ago (3 children)

Run Docker at the host level. Every level down from there is not only a knock to performance across the spectrum, it just makes a mess of networking. Anyone in here saying "it's easy to backup in a VM" has completely missed the point of containers, and apparently does not understand how to work with them.

You shouldn't ever need to backup containers, and if you're expecting data loss if one goes away, yerdewinitwrawng.

[–] Pika@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago)

Just chiming in, this is not recommended for proxmox

The documentation (FAQ 13) actually directly says that docker should be installed as a QEMU VM on proxmox and that it should not be installed on the Proxmox VE Host

[–] Oisteink@feddit.nl 2 points 2 days ago (1 children)

You dont need or want docker on your vm host. But a bare metal docker host can solve many peoples needs.

[–] just_another_person@lemmy.world -1 points 2 days ago

What in the world are you talking about? It's literally the entire point of containers orchestration systems, and the reason why you don't run containers inside containers. It's makes zero sense.

[–] possiblylinux127@lemmy.zip 0 points 2 days ago (1 children)

People are probably looking for tools like cloud init, butane and Ansible

[–] just_another_person@lemmy.world 1 points 2 days ago (1 children)

These should absolutely no place in the mix with containers at all. Very confused how you've made these work of that's what you're suggesting.

[–] possiblylinux127@lemmy.zip 1 points 2 days ago

No, I mean they should setup VMs and LXC containers in automated way. I get the impression that some people here are trying to use a Dockerfile instead of something like Ansible where the end changes apply to a end system instead of creating a template for temporary deployments.