PVE LXC Containers - Revision history

Tinker at 04:18, 1 October 2025

2025-10-01T04:18:57Z

← Older revision		Revision as of 00:18, 1 October 2025
Line 4:		Line 4:

	In fact, I have created a large set of containers on my testbed server simply by following the [[Server Building{{!}}Server Building]] outlines here on this site.		In fact, I have created a large set of containers on my testbed server simply by following the [[Server Building{{!}}Server Building]] outlines here on this site.

			''Heck... These days, I tend to default to Debian LXC containers unless there's a VERY good reason to do otherwise...''
	= Building a Container =		= Building a Container =
	== Templates ==		== Templates ==
Line 33:		Line 35:

	=== CLI method ===		=== CLI method ===
	* <code>pct create '''VMID''' '''TEMPLATE''' --hostname '''HOSTNAME''' --password '''PASSWORD''' --rootfs '''LOCATION''':'''SIZE''' --cores '''CORES''' --memory '''RAM''' --swap '''SWAP''' --unprivileged '''<1{{!}}0>''' --features '''nesting=<1{{!}}0>''' --net0 name='''eth0''',bridge='''BRIDGE''',firewall='''<1{{!}}0>''',ip='''<(IPv4/CIDR\|dhcp\|manual)>'''</code>		* <code>pct create '''VMID''' '''TEMPLATE''' --hostname '''HOSTNAME''' --password '''PASSWORD''' --rootfs '''LOCATION''':'''SIZE''' --cores '''CORES''' --memory '''RAM''' --swap '''SWAP''' --unprivileged '''<1{{!}}0>''' --features '''nesting=<1{{!}}0>''' --net0 name='''eth0''',bridge='''BRIDGE''',firewall='''<1{{!}}0>''',ip='''<(IPv4/CIDR{{!}}dhcp{{!}}manual)>'''</code>
	* EXAMPLE (same as defaults in UI, but DHCP for IPv4 & unique identifiers...):		* EXAMPLE (same as defaults in UI, but DHCP for IPv4 & unique identifiers...):
	** <code>pct create '''666''' '''local:vztmpl/debian-11-standard_11.6-1_amd64.tar.zst''' --hostname '''LXC-test''' --password '''nuggit''' --rootfs '''local-lvm''':'''8''' --cores '''1''' --memory '''512''' --swap '''512''' --unprivileged '''1''' --features '''nesting=1''' --net0 name='''eth0''',bridge='''vmbr0''',firewall='''1''',ip='''dhcp'''</code>		** <code>pct create '''666''' '''local:vztmpl/debian-11-standard_11.6-1_amd64.tar.zst''' --hostname '''LXC-test''' --password '''nuggit''' --rootfs '''local-lvm''':'''8''' --cores '''1''' --memory '''512''' --swap '''512''' --unprivileged '''1''' --features '''nesting=1''' --net0 name='''eth0''',bridge='''vmbr0''',firewall='''1''',ip='''dhcp'''</code>
Line 51:		Line 53:
	I'd suggest adding a regular user so that you can then SSH into the container.		I'd suggest adding a regular user so that you can then SSH into the container.

	I have a set of configurations that I do to pretty much every LXC container I build. Check [[CopyPasta#For_doing_basic_setup_of_an_LXC_(or_pretty_much_any_Linux_VM...):\|this entry]].		I have a set of configurations that I do to pretty much every LXC container I build. Check [[CopyPasta#For_doing_basic_setup_of_an_LXC_(or_pretty_much_any_Linux_VM...):{{!}}this entry]].

	=== Root Access via SSH ===		=== Root Access via SSH ===
Line 139:		Line 141:

	* <code>vi /etc/pve/lxc/112.conf</code>		* <code>vi /etc/pve/lxc/112.conf</code>

	lxc.cgroup2.devices.allow: c 10:200 rwm		lxc.cgroup2.devices.allow: c 10:200 rwm
	lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file		lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file

	If the LXC is already running it will need to be shut down and started again for this change to take effect.		If the LXC is already running it will need to be shut down and started again for this change to take effect.

Tinker: /* Using Tailscal on an LXC */

2025-09-16T22:55:55Z

Using Tailscal on an LXC

Tinker: /* Stumbling Blocks & Oddities */

2025-01-28T23:51:00Z

Stumbling Blocks & Oddities

← Older revision		Revision as of 19:51, 28 January 2025
Line 84:		Line 84:

	= Stumbling Blocks & Oddities =		= Stumbling Blocks & Oddities =
			== Time Zone Settings ==
			Apparently, LXCs default to UTC even if your server is set to your local timezone.

			Fortunately, it's not difficult to correct this.

			* <code>sudo dpkg-reconfigure tzdata</code>
			or
			* pick another method from [https://itslinuxguide.com/debian-set-timezone/ this web page].

	== DHCP / DNS Difficulties ==		== DHCP / DNS Difficulties ==
	For some reason, If I set up a container with both IPv4 & IPv6 using '''DHCP''', resolved will <span style="text-decoration: underline;">ONLY use IPv6</span>. This is kind of an issue if I want to use IPv4 DNS...		For some reason, If I set up a container with both IPv4 & IPv6 using '''DHCP''', resolved will <span style="text-decoration: underline;">ONLY use IPv6</span>. This is kind of an issue if I want to use IPv4 DNS...

Tinker: /* Adding NFS to an LXC */

2024-10-20T17:22:20Z

Adding NFS to an LXC

← Older revision		Revision as of 13:22, 20 October 2024
Line 119:		Line 119:

	Then go ahead & [[Setting up NFS for file sharing{{!}}set up NFS as normal]].		Then go ahead & [[Setting up NFS for file sharing{{!}}set up NFS as normal]].

			== Using Tailscal on an LXC ==
			LXCs do not give access to a '''/dev/tun''' device & this is needed for Tailscale to work.

			If you're running the LXC on Proxmox, You can add this feature by editing the containers configuration file.

			The following instructions are copied (and/or adapted) from [https://tailscale.com/kb/1130/lxc-unprivileged this page].

			For example, using Proxmox to host an LXC with ID 112, the following lines would be added to /etc/pve/lxc/112.conf:

			lxc.cgroup2.devices.allow: c 10:200 rwm
			lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file
			If the LXC is already running it will need to be shut down and started again for this change to take effect.

	= PVE CLI Tools for LXC work... =		= PVE CLI Tools for LXC work... =
	* pct (Proxmox Container Toolkit)		* pct (Proxmox Container Toolkit)
	* pveam (Proxmox VE Appliance Manager)		* pveam (Proxmox VE Appliance Manager)

Tinker: /* Further Tricks */

2024-07-28T20:51:04Z

Further Tricks

← Older revision		Revision as of 16:51, 28 July 2024
Line 77:		Line 77:

	Apparently, either [https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points "Bind Mount Points"] or [https://pve.proxmox.com/wiki/Linux_Container#_device_mount_points "Device Mount Points"] are the solution...		Apparently, either [https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points "Bind Mount Points"] or [https://pve.proxmox.com/wiki/Linux_Container#_device_mount_points "Device Mount Points"] are the solution...

			[https://forum.proxmox.com/threads/mount-external-hdd-in-lxc-container.50897/ This thread] and [https://forum.proxmox.com/threads/container-with-physical-disk.42280/ this one] have some helpful discussion...

	= Pre-Built Containers =		= Pre-Built Containers =

Tinker: /* Further Tricks */

2024-07-28T20:40:12Z

Further Tricks

← Older revision		Revision as of 16:40, 28 July 2024
Line 76:		Line 76:
	One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)		One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)

	Apparently, [https://pve.proxmox.com/wiki/Linux_Container#_device_mount_points Device Mount Points] are the solution...		Apparently, either [https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points "Bind Mount Points"] or [https://pve.proxmox.com/wiki/Linux_Container#_device_mount_points "Device Mount Points"] are the solution...

	= Pre-Built Containers =		= Pre-Built Containers =

Tinker: /* Further Tricks */

2024-07-28T20:38:20Z

Further Tricks

← Older revision		Revision as of 16:38, 28 July 2024
Line 76:		Line 76:
	One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)		One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)

	Apparently, [https://pve.proxmox.com/wiki/Linux_Container#~~_bind_mount_points Bind~~ Mount Points] are the solution...		Apparently, [https://pve.proxmox.com/wiki/Linux_Container#_device_mount_points Device Mount Points] are the solution...

	= Pre-Built Containers =		= Pre-Built Containers =

Tinker: /* Root Access via SSH */

2024-07-28T20:33:50Z

Root Access via SSH

← Older revision		Revision as of 16:33, 28 July 2024
Line 73:		Line 73:
	(In theory, you should be able to [[HowTo -_ssh#Make_it_easier_to_connect{{!}}set up the public key normally]] now & then revert the ssh_config change.)		(In theory, you should be able to [[HowTo -_ssh#Make_it_easier_to_connect{{!}}set up the public key normally]] now & then revert the ssh_config change.)

	== Further Tricks ===One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)		== Further Tricks ==
			One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)

	Apparently, [https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points Bind Mount Points] are the solution...		Apparently, [https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points Bind Mount Points] are the solution...

Tinker: /* Further Tricks = */

2024-07-28T20:33:01Z

Further Tricks =

← Older revision		Revision as of 16:33, 28 July 2024
Line 73:		Line 73:
	(In theory, you should be able to [[HowTo -_ssh#Make_it_easier_to_connect{{!}}set up the public key normally]] now & then revert the ssh_config change.)		(In theory, you should be able to [[HowTo -_ssh#Make_it_easier_to_connect{{!}}set up the public key normally]] now & then revert the ssh_config change.)

	== Further Tricks ===		== Further Tricks ===One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)
	One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)
			Apparently, [https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points Bind Mount Points] are the solution...

	= Pre-Built Containers =		= Pre-Built Containers =

Tinker: /* Configuring & Using the Container */

2024-07-28T20:31:35Z

Configuring & Using the Container

← Older revision		Revision as of 16:31, 28 July 2024
Line 72:		Line 72:
	* <code>service ssh restart</code>		* <code>service ssh restart</code>
	(In theory, you should be able to [[HowTo -_ssh#Make_it_easier_to_connect{{!}}set up the public key normally]] now & then revert the ssh_config change.)		(In theory, you should be able to [[HowTo -_ssh#Make_it_easier_to_connect{{!}}set up the public key normally]] now & then revert the ssh_config change.)

			== Further Tricks ===
			One useful trick is to add storage to the LXC that's not managed by PVE directly. (For instance, I'm building an LXC for use in backing up & reconfiguring local machines & VMs. I'd like to use a dedicated drive in a hot-swap bay on my server.)

	= Pre-Built Containers =		= Pre-Built Containers =

← Older revision		Revision as of 18:55, 16 September 2025
Line 129:		Line 129:
	Then go ahead & [[Setting up NFS for file sharing{{!}}set up NFS as normal]].		Then go ahead & [[Setting up NFS for file sharing{{!}}set up NFS as normal]].

	== Using ~~Tailscal~~ on an LXC ==		== Using a VPN (OpenVPN or TailScale) on an LXC ==
	LXCs do not give access to a '''/dev/tun''' device & this is needed for Tailscale to work.		LXCs do not give access to a '''/dev/tun''' device & this is needed for Tailscale to work.

Line 137:		Line 137:

	For example, using Proxmox to host an LXC with ID 112, the following lines would be added to /etc/pve/lxc/112.conf:		For example, using Proxmox to host an LXC with ID 112, the following lines would be added to /etc/pve/lxc/112.conf:

			* <code>vi /etc/pve/lxc/112.conf</code>

	lxc.cgroup2.devices.allow: c 10:200 rwm		lxc.cgroup2.devices.allow: c 10:200 rwm
	lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file		lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file

	If the LXC is already running it will need to be shut down and started again for this change to take effect.		If the LXC is already running it will need to be shut down and started again for this change to take effect.

			* <code>pct reboot 112</code>

	= PVE CLI Tools for LXC work... =		= PVE CLI Tools for LXC work... =
	* pct (Proxmox Container Toolkit)		* pct (Proxmox Container Toolkit)
	* pveam (Proxmox VE Appliance Manager)		* pveam (Proxmox VE Appliance Manager)