[crimsonnoodle58]

Careful. I too thought about this, but docker containers have the following benefits over the LXC scripts:

- Updates and automatic upgrades between major versions.

- The developer who wrote the software created the container (most of the time), this means its a supported environment. Also, as they have the insight into the application and future upgrades the environment has been setup correctly for each version.

If you want to achieve your goal, I'd suggest an LXC with your favourite Linux distro + docker + app container(s) for each app you have. It gives you the same thing, but with the benefits above.

[fazeirony]

i too was looking at going the route of the poster above. is your suggestion essentially the 'same' in terms of resources as converting a docker container to a LXC (relatively speaking)? for some reason i had/have it in my head that the LXC's would somehow be more efficient (based on...nothing, hence the question!)

[crimsonnoodle58]

Think of an LXC as a docker container but at the OS level.

An LXC running docker with an app containerised inside will basically be the same as if the app is running a level higher in the LXC itself.

Give it a try. Then open top/htop in the host OS (pve shell) and you'll see the apps running in the docker container inside the LXC as native processes.

[fazeirony]

tyty!

i'm setting up a new server soon and want to optimize/correct some of the things i've done on my first proxmox setup (like not running truenas in proxmox passing the RAID controller through lol).

i'll give this a shot!

[IseardMi]

Oh yeah I definitely won't be doing this for all my containers, the majority will stay within my VM. However it is worth noting that in many cases the LXC scripts install most of the required packages by adding their official repositories, so this seems like a well supported way of doing this.