LXC containers on Proxmox: many services, little memory
An LXC container starts in a second and costs a fraction of what a virtual machine reserves.
Starting at from €13.99/mo
Introduction
An LXC container emulates no machine: it shares the host kernel and carries only the distribution's filesystem. The direct consequence is that it starts almost instantly and uses what it actually needs, where a virtual machine reserves its memory up front whether it uses it or not.
The gap shows quickly. On a 16 GB VDS at €13.99/month, four full VMs are cramped; twenty containers hosting small services live there without effort. Proxmox VE manages them from the same interface as VMs, with the same snapshots and the same backups.
The price of that saving is worth knowing: isolation is weaker. Since the kernel is shared, a container cannot load its own kernel module, and a kernel flaw touches everyone. For code you do not control, or for a non-Linux system, a VM remains the right tool.
What the server brings, across the whole range
Proxmox VE already installed
The server arrives with <strong>Proxmox VE</strong> in place and its web interface reachable. You create your virtual machines and LXC containers from the browser, without a support ticket or a wait. <strong>Reinstalls are unlimited</strong>: an experiment that goes wrong is redone in minutes.
RAM, because that is what runs out first
On a hypervisor it is almost never the processor that caps out first: it is <strong>memory</strong>, because every virtual machine reserves its own. The range starts at <strong>16 GB</strong> and goes up to <strong>96 GB</strong>, which leaves room to stack several VMs without starving them.
Unlimited snapshots and backups
A snapshot before an update, another before a configuration change: that is what separates a test from a gamble. Neither the count nor the frequency is billed, so nothing discourages taking one more.
Up to 16 additional IPv4 addresses
Each VM can hold its own public address, which avoids routing everything through port forwards on the host. Useful as soon as a virtual firewall, a web server and a third-party service have to coexist cleanly.
Where LXC is the right call
One site per container
Ten client sites, ten containers, each with its web stack and PHP version. They do not tread on each other and cost about what a single shared server would.
Supporting services
Redis, a message broker, an application cron, a metrics collector. Each deserves isolation, none deserves 2 GB reserved for life.
Development environments
One container per branch or language version. It is created from a template in seconds and destroyed without regret.
A front-facing reverse proxy
A light container carrying Nginx or Traefik and dispatching to the rest. Restarting the front end touches nothing else.
Replace underused VMs
Plenty of VMs run with 4 GB reserved for a service using 300 MB. Converting them to containers frees the memory at once, without changing plan.
Frequently asked questions
A VM emulates a whole computer and loads its own kernel: strong isolation, reserved memory. An LXC container shares the host kernel: instant start, memory used on demand, weaker isolation.
No. LXC shares the host's Linux kernel, so it can only carry Linux systems. For Windows you need a virtual machine — Proxmox does that very well on the same server.
Yes, Proxmox treats them the same way: snapshots and backups from the same interface, with no limit on count or frequency here.
They answer different questions. LXC carries a complete system you administer like a machine; Docker packages an application and its environment. Many people install Docker inside a VM on the same server.