Proxmox: LXC Using External Templates

In this post, I show you how to create Linux Containers using alternative container template registries.

10 days ago • 3 min read

LXC the Typical Way

Typically in Proxmox, you would create a Linux Container by first updating the database using this command in PVE:

pveam update

Update the Linux Container database

Then, you'd choose your designated storage volume for Linux Container templates, for example:

Finally, you'd browse the list of Linux Container templates and download your preferred image:

From there, when you go to create a new container, you choose your downloaded image as the base and proceed with your installation.

Using External Templates

Why would you want to do this?
It's fair to say that the list of container templates in PVE is extensive, containing most of the common Linux distributions; as well as a lengthy list of TurnKey images.

However, there are other image repositories that make available many more options for your Linux Container needs. Here is a couple for starters:

Using the Linux Mint base as an example, here is how you would use that to create Linux Containers in Proxmox.

Considerations

Managed vs. Unmanaged Containers

That there is a list of official containers supported by Proxmox is not for nothing. These are containers that the developers have added to tightly integrate with the Linux Container subsystem in Proxmox.

Proxmox VE tries to detect the Linux distribution in the container, and modifies some files. Here is a short list of things done at container startup...

Linux Container - Proxmox VE

Proxmox VE

Most modifications are OS dependent, so they differ between different distributions and versions. You can completely disable modifications by manually setting the ostype to unmanaged.

If you use on of the container templates in the links mentioned above, you may want to ensure the proper ostype is set in /etc/pve/lxc/<ct-id>.conf.

Choose Your Image Base

Proceed through the following order directories: Mint > {VERSION_NAME} > amd64 > default > {DATE}. From my research, the difference between cloud and default is one contains support for cloud-init while the other doesn't.