Proxmox: Create and Use LXC Containers – Step-by-Step Guide for Beginners

After you have installed Proxmox VE in the previous article and successfully set up your first virtual machine, Proxmox offers another exciting option: LXC containers. This powerful and resource-efficient virtualization technology is particularly suitable for use cases where you do not need a complete virtual server but still want to operate an isolated Linux environment.

LXC (Linux Containers) is a container technology that allows you to run multiple independent Linux systems on a single host. Unlike virtual machines, containers do not require their own kernel or operating system – they share these resources with the host while remaining isolated from each other. This makes them lightweight and gives you the ability to efficiently deploy services such as web servers, databases, or development environments.

In this step-by-step guide, we dive into the world of LXC containers in Proxmox. You will learn everything from setting up a container to managing and using it. We explain the concepts in an understandable way and offer practical examples so you can get started directly without prior knowledge. Whether you run a homelab or take your first steps toward server virtualization – this guide gives you the tools to successfully integrate LXC containers into your Proxmox environment.

What Are LXC Containers?

LXC (Linux Containers) is a lightweight virtualization technology that allows you to run isolated Linux environments directly on your host system.

Containers share the kernel of the host system, making them significantly more resource-efficient than virtual machines. They do not emulate a complete operating system, but provide their own isolated runtime environment that is perfectly suited for applications where performance and efficiency are critical.

┌─────────────────────────────────────────────────────────────┐
│                 LXC CONTAINER VS. VIRTUAL MACHINE           │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│   LXC Container (Operating System Virtualization)           │
│   ┌─────────────────────────────────────────────────────┐   │
│   │   Applications & Services (Apache, MySQL, Node.js)  │   │
│   ├─────────────────────────────────────────────────────┤   │
│   │   Own Libraries & Rootfs (Debian / Alpine)          │   │
│   ├─────────────────────────────────────────────────────┤   │
│   │   Shared Host Linux Kernel (Namespaces/Cgroups)     │   │
│   └─────────────────────────────────────────────────────┘   │
│   * Starts in seconds  * Minimal RAM & disk requirements    │
│                                                             │
│   KVM Virtual Machine (Hardware Virtualization)             │
│   ┌─────────────────────────────────────────────────────┐   │
│   │   Applications & Services                           │   │
│   ├─────────────────────────────────────────────────────┤   │
│   │   Own complete guest operating system               │   │
│   ├─────────────────────────────────────────────────────┤   │
│   │   Own guest kernel & virtual drivers                │   │
│   ├─────────────────────────────────────────────────────┤   │
│   │   Virtual Hardware (QEMU Hypervisor)                │   │
│   └─────────────────────────────────────────────────────┘   │
│   * Full kernel isolation  * Higher overhead (GB range)     │
│                                                             │
└─────────────────────────────────────────────────────────────┘

An LXC container behaves like a small Linux system in which you can install programs, start services, or manage files – all in an isolated environment.

This technology is ideal for:

• Web servers: Deploy Apache or Nginx without running a VM.
• Databases: Use MySQL or PostgreSQL efficiently.
• Development environments: Develop and test software securely and resource-efficiently.

Advantages Over Virtual Machines

LXC containers offer numerous advantages over traditional virtual machines. They are particularly suitable for use cases where efficiency is paramount and full machine virtualization is not required.

Lower Resource Consumption

Containers require neither their own kernel nor a complete operating system. Instead, they share the kernel of the host system.

This makes them significantly more resource-efficient:

• RAM: A container often requires less than 512 MB, while a VM requires at least 1–2 GB.
• Disk Space: Containers are very small (often under 1 GB), while a VM requires several GB.

Typical Resource Comparison:

• Container: 128–512 MB RAM and 0.5–2 GB storage
• Virtual Machine (VM): 1–2 GB RAM and 10–20 GB storage

Faster Start

While a VM can take several minutes to start, a container starts in a few seconds. This is particularly useful when you need to quickly deploy new environments or run a large number of containers simultaneously.

Higher Density

On the same hardware, you can run significantly more containers than virtual machines. This makes containers ideal for scenarios where resources are limited or numerous small services are needed.

Easier Management

Containers are easier to create and manage than virtual machines. They require less configuration and are easy to clone, back up, and restore.

Efficient Use of Network Resources

Containers have direct access to the host's network resources and require less overhead for managing network connections. This makes them particularly efficient for applications such as web servers or databases.

Ideal for Specialized Applications

Containers are excellent for services that require an isolated environment but do not need their own kernel or comprehensive virtualization.

Examples include:

• Web servers (e.g. Apache, Nginx)
• Databases (e.g. MySQL, PostgreSQL)
• Development and testing environments

Prerequisites

Before you start setting up LXC containers on your Proxmox host, you should make sure your system meets the necessary prerequisites. This section helps you prepare everything for a smooth start.

Proxmox VE Installed

You should have a working installation of Proxmox VE. If you have not set this up yet, we recommend our Proxmox installation guide, where we explain all steps in detail.

Network Configuration

Containers require a working network connection:

1. DHCP: If you operate a router in your network that supports DHCP, containers are usually automatically assigned an IP address. This works without problems for most home server scenarios.
2. Static IP Addresses: If you want to run containers with fixed IP addresses, you should make sure your network supports this and you have enough free IPs. This is particularly useful for services such as web servers or databases.

Storage Space

Containers require little storage space, but your Proxmox host should still have sufficient capacity:

• local (lvm): The default storage location in Proxmox where containers store their disk or storage files. Make sure there is enough space available on local (lvm).

💡 Tip: For multiple small containers, at least 10–20 GB of free storage should be available.

Internet Access

A working internet connection on your Proxmox host is required to download container templates. Without internet access, you cannot add new templates.

Templates

Containers are based on pre-built operating system templates. Make sure you have downloaded at least one template before creating your first container. How to download templates is explained in the next section.

Basic Knowledge

While this guide does not require deep knowledge, basic Linux concepts such as file systems, network terms, and simple commands are helpful. This makes container management and installing additional software in your containers easier.

Container Templates

LXC containers in Proxmox are based on pre-built container templates that contain images of Linux operating systems. These templates are the basis for creating containers and must be downloaded before use. In this section, we explain how to easily add templates via the Proxmox web interface.

Access the Template List

1. Log in to the Proxmox web interface: Open your browser and go to https://<proxmox-ip>:8006. Log in with the user root and your set password.
2. Select your node from the list on the left side.
3. Click on the entry "local (pve)" or another storage location used for containers.
4. Select "CT Templates" in the right area.

Storage Selection in the Web GUI:

• Left navigation tree: Select node $\rightarrow$ local (pve)
• Right main window: Click on the CT Templates tab
• Action area: Manage and download templates centrally

Download Template

1. Click on "Templates" in the top right to open the list of available templates.
2. You will see a variety of Linux distributions available for containers:

• Debian (e.g. debian-11-standard / debian-12-standard): Ideal for server applications.
• Ubuntu (e.g. ubuntu-22.04-standard / ubuntu-24.04-standard): Flexible distribution for almost all use cases.
• CentOS / AlmaLinux / Rocky Linux: Perfect for enterprise applications.
• Alpine Linux: An extremely lightweight and resource-efficient system.

1. Select a template from the list, e.g. debian-11-standard, and click "Download". Proxmox starts downloading the template, and you can track the progress.

After the download is complete, the template appears in the list under "CT Templates".

Download Multiple Templates

It makes sense to download multiple templates to stay flexible. This way you can create suitable containers for different use cases:

• Debian 11 / 12: Stable and reliable for web servers or databases.
• Ubuntu 22.04 / 24.04: Current and widely used, ideal for developers.
• Alpine Linux: Perfect for resource-saving services like proxy servers.

Tips for Selecting Templates

When choosing a template, you should consider the following criteria:

• Use Case: For simple services, a lightweight system like Alpine Linux is sufficient, while Debian or Ubuntu are better suited for more complex systems.
• Compatibility: Make sure the desired software is compatible with the container's operating system.

Understanding Template Types

After you have downloaded the required templates, it is important to understand what types of templates exist and how they can be used for different use cases.

Standard Templates

Standard templates are pre-built images of popular Linux distributions such as Debian, Ubuntu, CentOS, or Alpine Linux. They typically contain a basic system installation with minimal software.

• Advantages:
• Minimal storage requirements.
• Fast setup and easy configuration.
• Perfect for general applications.

💡 Examples:

• debian-11-standard – Ideal for stable server applications.
• ubuntu-22.04-standard – Flexible and widely used.
• centos-8-standard – Suitable for enterprise software.

Minimal Templates

Minimal templates contain even less pre-installed software than standard templates. They are suitable for experts who want to customize containers precisely to their needs.

• Advantages:
• Extremely lean and resource-efficient.
• Optimal for experienced users who want to configure everything from scratch.
• Disadvantage:
• It can be more time-consuming to manually install the required services and packages.

💡 Examples:

• debian-11-minimal – Only basic functions; ideal for heavily customized applications.
• alpine-minimal – Very lightweight for small services.

Special Templates

Special templates are specifically compiled images for certain use cases or pre-configured environments. They often contain additional software packages or services directly after installation.

• Advantages:
• Provision of pre-configured services.
• Time savings during setup.

💡 Examples:

• nginx-template – A pre-configured web server with Nginx.
• mysql-template – Database server ready for immediate use.

When Do I Use Which Template Type?

• Standard Templates: When you need a stable environment and want to deploy services such as web servers, databases, or development environments.
• Minimal Templates: When you want maximum control over your container and can handle installing the required software yourself.
• Special Templates: For quick deployments of certain services or pre-configured environments without spending much time on configuration.

Template Management

After you have downloaded the first templates, it is useful to know how to manage them in Proxmox.

View Templates

1. Navigate to your storage location: Open the Proxmox web interface and select the appropriate storage location on the left, e.g. "local" or "local-lvm".
2. View CT Templates: Click on the "CT Templates" (Container Templates) tab to see a list of all downloaded templates. You will see all installed templates on this storage, e.g. debian-11-standard or ubuntu-22.04-standard.

Delete Templates

If a template is no longer needed, you can delete it to free up storage space:

1. Select the template you want to remove from the list under "CT Templates".
2. Click on "Remove" at the top.
3. Confirm the deletion in the dialog that appears.

💡 Tip: Only delete templates you are sure you no longer need, as they will need to be re-downloaded if you want to use them again later.

Update Templates

Templates can occasionally be updated to integrate new features or security updates of the underlying operating systems:

1. Check if a newer version is available: Go to "CT Templates" and click on "Templates" to display the list of available templates again. If a new version of one of your existing templates is available, it will be displayed at the top of the list.
2. Download new template: Download the new template by clicking "Download". The old template remains until you manually delete it.

Change Storage Location for Templates

By default, templates are stored in the storage defined during Proxmox installation (e.g. local). However, you can also specify a different storage location:

1. Go to "Datacenter" > "Storage".
2. Click on "Add" to add an additional storage location (e.g. NFS or another local drive).
3. Configure the new storage location to be suitable for container templates: Check the box for "Container Template".
4. Save the changes.

💡 Tip: When you download next time, you can select the new storage location to store templates there.

Configure Container

After you have downloaded the required templates and created the basic prerequisites, it is time to configure your first LXC container.

Create Container

There are two ways to create a new container:

• Right-click on your node (your server name) and select "Create CT".
• Alternatively, you can click on the blue "Create CT" button in the top right.

Options for Container Creation:

• Option 1: Right-click on the node in the left menu tree $\rightarrow$ Create CT
• Option 2: Blue button top right in the web interface $\rightarrow$ Create CT

General Settings

In the first tab "General", you set the basic data for your container:

1. Node: Your server name (node) is pre-selected. Only with multiple nodes you need to select where the container should be created.
2. CT ID: The container ID is automatically suggested (e.g. 101). You can adjust it as needed, each ID may only be assigned once.
3. Hostname: Give the container a name, e.g. webserver-container. Use only lowercase letters, numbers, and hyphens (no spaces or special characters).
4. Unprivileged Container: Check the box for "Unprivileged container" for more security (recommended for almost all use cases).
5. Nesting: If you want to run containers within the container (nested), enable "Nesting". For most beginner projects, this is not necessary.
6. Resource Pool: Can usually be ignored unless you use multiple pools in Proxmox for resource management.
7. Password / Confirm password: Set a strong password for the default user root in the container and confirm it in the second field.
8. SSH public key(s): Optional: Add your public SSH key here if you want to access the container via key instead of password.

Recommended Example Configuration (General):

• Node: proxmox-node
• CT ID: 101
• Hostname: webserver-container
• Unprivileged container: enabled (recommended)
• Nesting: disabled (default)
• Resource Pool: leave empty (optional)
• Password: set secure password
• Confirm password: confirm password
• SSH public key(s): leave empty (optional)

Click "Next" to continue with template selection.

Select Template

In the second tab "Template", you determine which operating system the container will be created with.

1. Storage: Select the storage where your CT templates are located, e.g. local or local-lvm.
2. Template: Open the dropdown menu and select the desired template, e.g. debian-12-standard or ubuntu-22.04-standard.

Click "Next" to proceed to disk configuration.

Configure Disk

In the third tab "Disks", you determine which storage your container will be placed on and how much space it will receive.

1. Storage: Select the storage location from the dropdown menu, e.g. local-lvm or local.
2. Disk size (GiB): Specify how much storage space your container should receive, e.g. 8 or 10 GiB.
3. Advanced (optional): Here you can set special mount options, ACLs (access control lists), or "Skip Replication". For beginners and initial tests, the default options are ideal.

Recommended Disk Configuration:

• Storage: local-lvm
• Disk size: 10 GiB
• Advanced: keep default options

Click "Next" to proceed to CPU configuration.

Configure CPU

In the fourth tab "CPU", you set how much computing power your container may use.

1. Cores: Specify how many CPU cores should be assigned to the container, for example 1 or 2.
2. CPU Limit (optional): Here you can specify a percentage value to limit the maximum CPU usage of the container.
3. CPU Units: Indicates the priority of your container compared to other containers. Default value is 1024.

Recommended CPU Configuration:

• Cores: 1
• CPU Limit: leave empty (no limit)
• CPU Units: 1024 (default)

Click "Next" to proceed to memory configuration (RAM).

Configure RAM

In the fifth tab "Memory", you determine how much memory (RAM) and swap memory your container may use.

1. Memory (MiB): Specify how much RAM should be assigned to the container, e.g. 512 or 1024 MiB.
2. Swap (MiB): Swap is overflow memory used when the available RAM is exhausted. A typical value is about half to as much as the assigned RAM.

Recommended Memory Configuration:

• Memory (MiB): 512
• Swap (MiB): 256

Click "Next" to proceed to network configuration.

Configure Network

In the sixth tab "Network", you set how your container communicates with the network.

1. Name: By default, this is eth0. For most cases, this does not need to be changed.
2. MAC Address: A MAC address is automatically generated here. You can leave this value on "auto".
3. Bridge: Select the network bridge to which the container will be connected. Usually this is vmbr0, the default bridge of Proxmox.
4. VLAN Tag: Can be left empty unless you use VLANs in the network.
5. Firewall: The checkbox is set by default. With the Proxmox firewall, you can control network access to the container.
6. IPv4: Select DHCP so that the container automatically receives an IP from the router/network. Alternatively, you can select Static and enter a fixed IP, subnet (CIDR), and gateway.
7. IPv6: For beginners, this setting can usually remain on None.

Recommended Network Configuration:

• Name: eth0
• MAC Address: auto
• Bridge: vmbr0
• VLAN Tag: leave empty
• Firewall: enabled (default)
• MTU: Same as bridge
• IPv4: DHCP (or Static)
• IPv4/CIDR: empty or e.g. 192.168.1.100/24
• Gateway (IPv4): empty or e.g. 192.168.1.1
• IPv6: None
• Rate Limit: leave empty

Click "Next" to proceed to DNS configuration.

Configure DNS

In the seventh tab "DNS", you set the domain and DNS servers for the container.

1. DNS domain: Optional. Here you can enter a local or internal domain, e.g. home.lan.
2. DNS servers: Enter the IP address(es) of the DNS server that the container should use for hostname resolution. Proven examples: your router's address (192.168.1.1) or public DNS servers like 8.8.8.8 (Google) and 1.1.1.1 (Cloudflare).

Click "Next" to proceed to the summary.

Summary and Container Creation

In the last tab "Summary", you will receive an overview of all settings. Here you can review everything again before the actual creation begins.

1. Review: Look at the summary carefully: storage location, template, disk size, CPU, RAM, and network settings, DNS, etc.
2. Start container after creation: At the bottom of the window there is the option "Start after created". This is usually pre-selected – your container will then start automatically after successful creation.
3. Create: If everything is correct, click "Finish". Proxmox now creates the container with your settings.
4. Start container (if not automatic): If you deselected automatic starting, you can select your container in the left menu afterwards and click "Start".
5. Access the console: After starting, you can access the container by selecting it in the left tree view and clicking "Console" in the main window. Here you can now log in with the set root password.

❗ Congratulations! You have successfully created and configured your first LXC container.

Assign Resources

After your container has been created and started, you can assign additional resources or adjust existing settings as needed.

Adjust CPU and RAM

1. Click on your container in the left tree.
2. Switch to the "Resources" tab at the top.
3. Click on the respective entry ("Memory", "Core") and select "Edit".
4. Now you can increase or decrease the number of cores, the CPU limit, the CPU units, and the memory (Memory) as needed. The change becomes active immediately after saving.

Expand Root Disk

1. In the "Resources" tab, the root disk (e.g. rootfs) is displayed.
2. Click on it, then on "Volume Action" in the top right, and select "Resize".
3. Enter the desired new size in GiB (only larger possible, e.g. from 10 to 15 GiB).

⚠️ Warning: Reducing is not possible directly!

Add Mount Points or Passthrough Devices

Via "Add" in the "Resources" tab, you can:

• Add an additional mount point (useful if you want to integrate additional storage areas).
• Add device passthrough if special hardware should be passed directly to the container (e.g. USB devices).

Adjust or Extend Network

1. Switch to the "Network" tab.
2. Select the existing adapter and click "Edit". Here you can adjust all settings as during container setup.
3. Click on "Add" at the bottom of the "Network" tab to configure an additional network adapter.

💡 Tip: All changes take effect immediately. Proxmox dynamically adjusts the resources – so you can always respond flexibly to new requirements.

Manage Container

After your container is set up, it's now about basic everyday operation.

Start and Stop

You can easily start, stop, or restart containers in Proxmox in two ways.

Context Menu (Right-click): Right-click on your container in the left tree and select an action:

• Start – Turn on container
• Shutdown – Orderly shutdown
• Stop – Stop immediately
• Reboot – Restart
• Pause – Pause container

Buttons in the Main Window: Select the container with a left-click in the tree and click on the green "Start" button in the top right. Directly next to it you will find a dropdown menu with additional actions such as Shutdown, Pause, Hibernate, Stop, and Reset.

Container Control Options:

• Via context menu (right-click on container):
• Start – Turn on container
• Shutdown – Orderly ACPI shutdown
• Stop – Immediate hard power-off
• Reboot – Clean restart
• Pause – Freeze running state
• Via the navigation bar top right:
• Start button for direct start
• Dropdown menu with Shutdown, Pause, Hibernate, Stop, and Reset

This way you always maintain full control over the operating state of your containers.

Console & Access

Once your container is running, you have several ways to access it directly:

1. Web console via the Proxmox interface: Select your container in the left tree and click on the "Console" tab at the top. A terminal window opens directly in the browser.
2. Quick access via the context menu: Right-click on the container and select ">_ Console" from the menu.
3. SSH access from your own computer: To access the container via SSH, you need the container's IP address. First log in to the container's web console and enter the command:

ip a

or

ip addr

Note the displayed IP address for the network interface (usually eth0). Now you can establish a connection from your computer via the terminal:

ssh root@<your-container-ip>

💡 Tip: With the web console in the Proxmox interface, you always reach your container – even if no network connection exists yet. SSH is particularly practical when you regularly need remote access.

Install Software

A great advantage of LXC containers is that they feel like full-fledged Linux systems and you can install software normally.

1. Log in via web console or SSH.
2. Update system:

apt update && apt upgrade -y

1. Install software:

# Install web server
apt install apache2 -y

# Install database server
apt install mariadb-server -y

# Install Python runtime
apt install python3 -y

# Install text editor nano
apt install nano -y

1. Start and test services:

systemctl status apache2
systemctl restart apache2

💡 Note: All software packages available for the distribution used can be installed and used in the container – classic Linux feel, but resource-efficient!

Shut Down or Delete Container

Shut down container: Select the desired container in the left tree and click on the dropdown menu next to the "Start" button at the top and select "Shutdown".

Restart container: Via the same dropdown menu or the context menu via right-click, you can select "Reboot".

Delete container:

1. Make sure you have backed up all important data from the container!
2. Select the desired container in the left tree.
3. Click on the "More" dropdown menu in the top right area of the Proxmox window.
4. Select "Remove" from the dropdown menu.

⚠️ Warning: Proxmox will ask you for security if you really want to delete. After your confirmation, the container including all data will be removed. Deleting a container cannot be undone – so check carefully that you have backed up everything.

Advanced Features

After you know the basics of container management, you may want to benefit from some advanced options.

Privileged vs. Unprivileged Containers

• Unprivileged containers: Are recommended by default and are more secure as they have fewer privileges on the host. Many typical services run without restrictions.
• Privileged containers: Have more privileges and are suitable for special scenarios, e.g. when special system functions or software are required. Caution: They are less secure and should only be used with care!

⚠️ Warning: The setting is made when creating the container and cannot be easily changed afterwards (a new installation is required).

Set Up Bind Mounts

With bind mounts, you can directly mount folders from the Proxmox host into the container – ideal for sharing data:

1. Select your container, go to the "Resources" tab.
2. Click on "Add" > "Mount Point".
3. Enter the path on the host (e.g. /mnt/data) and the path in the container (e.g. /mnt/hostdata).
4. Save the change and restart the container if necessary.

💡 Tip: Bind mounts are very practical for backup directories, media data, or exchanging large files between multiple containers.

Other Practical Features

• Clone: Create an exact copy of an existing container – ideal for tests, backups, or similar setups.
• Convert to template: Transform an existing container into a template to quickly create new, identical containers from it.

Glossary of Technical Terms (LXC and Proxmox)

Command Reference (Cheatsheet)

Further Resources

Conclusion

With LXC containers, Proxmox provides you with an enormously powerful and at the same time resource-efficient way to run various Linux services on your server. Thanks to the clear Proxmox interface, creation and management are easy to master even for beginners. Whether for web servers, databases, development environments, or small private services: LXC containers allow you maximum flexibility with minimal overhead.

If you have become curious: Try the next steps, experiment with new templates, and discover how easily you can expand your home or test lab with Proxmox. With the linked resources, you will quickly find further help and answers to specialized questions.

Have fun virtualizing – and good luck with your first LXC containers on Proxmox!

👉 Course Overview: All Proxmox VE Articles & Guides