Talk:Proxmox Linux Container

NixOS container (LXC) on Proxmox Virtual Environment 7

	WUI	CLI	Reference
find the (a current) NixOS template	for example for 21.05 go to the hydra https://hydra.nixos.org/ find (in the row) nixos and choose it https://hydra.nixos.org/project/nixos currently (20.09 and) 21.05 is provided find your preferred channel to install (the newest stable release is 21.05 in the following) and choose it https://hydra.nixos.org/jobset/nixos/release-21.05 find (the tab) Jobs and choose it https://hydra.nixos.org/jobset/nixos/release-21.05#tabs-jobs find (in the row) nixos.containerTarball.x86_64-linux and choose it https://hydra.nixos.org/job/nixos/release-21.05/nixos.containerTarball.x86_64-linux find (in the row) the last successful build (the newest today is 155685206 in the following) and choose it https://hydra.nixos.org/build/155685206 find (in the row) the file nixos-system-x86_64-linux.tar.xz with the link https://hydra.nixos.org/build/155685206/download/1/nixos-system-x86_64-linux.tar.xz the link for the latest (daily) tarball for a container (of 21.05) is https://hydra.nixos.org/job/nixos/release-21.05/nixos.containerTarball.x86_64-linux/latest/download-by-type/file/system-tarball
download the NixOS template	(if you want to switch to the Storage View and) go to one of your nodes where you can (find and) store CT Templates. choose the Download from URL button add the link for the NiixOS template file https://hydra.nixos.org/job/nixos/release-21.05/nixos.containerTarball.x86_64-linux/latest/download-by-type/file/system-tarball (to the text field of `URL:`) add a nice file name for the current downloadable build of the template (to the text field of `File name:`) for example nixos-21.05_2021-10-10.tar.xz (Proxmox Virtual Environment style: name of the linux operating system (nixos), release version (21.05), and enriched with the date of the day of the (download and) build	going to the folder where all the templates for Promox Virtual Environment are stored `cd /mnt/pve/cephfs/template/cache` downloading the NixOS template file `wget -c https://hydra.nixos.org/job/nixos/release-21.05/nixos.containerTarball.x86_64-linux/latest/download-by-type/file/system-tarball` (optional you should) move the downloaded NixOS template file to a nicer (more individual) file name `mv system-tarball nixos-21.05_2021-10-10.tar.xz` (optional you can) going back `cd -`
create a (first) new NixOS container with Proxmox Virtual Environment	(if you want to switch to the Folder View and go to Nodes and choose the your nodes where you create the container. (this note will be preselected as Node in the form.)) choose the Create CT button tab `General` (for the following we expect) 1000 is prefilled (to the text field of `CT ID:`) or you have added it (because it not already taken) ~~(for the following we expect) the checkbox `Unprivileged container:` is preselected choosen~~ ~~(for the following we expect) the checkbox `Nesting:` is preselected choosen~~ add a (useless, but from the form required) passphrase (to the text field of `Password:`) add the same (useless, but from the form required) passphrase (to the text field of `Confirm password:`) (optional you can) add other options of the form, like the node for the container (at the drop down menu of `Node:`) the name for the container (to the text field of `Hostname:`) … choose the Next button tab `Template` (for the following we expect) the entry cephfs is prefilled (at the drop down menu of `Storage:`) (for the following we expect you) find and choose the entry nixos-21.05_2021-10-10.tar.xz (at the drop down menu of `Storage:`) choose the Next button tab `Root Disk` (for the following we expect) the entry storage is prefilled (at the drop down menu of `Storage:`) (for the following we expect) 8 is prefilled (to the text field of `Disk size (GiB):`) choose the Next button tab `CPU` (for the following we expect) 1 is prefilled (to the text field of `Cores:`) choose the Next button tab `Memory` (for the following we expect) 512 is prefilled (to the text field of `Memory (MiB):`) (for the following we expect) 512 is prefilled (to the text field of `Swap (MiB):`) choose the Next button tab `Network` (for the following we expect) eth0 is prefilled (to the text field of `Name:`) ~~(for the following we expect) (the text field of `MAC address:`) is emtpy (and so prefilled with auto)~~ (for the following we expect) the entry vmbr0 is prefilled (at the drop down menu of `Bridge:`) ~~(for the following we expect) (the text field of `VLAN Tag:`) is emtpy (and so prefilled with no VLAN)~~ ~~(for the following we expect) (the text field of `Rate limit (MB/s) Tag:`) is emtpy (and so prefilled with unlimited)~~ ~~(for the following we expect) the checkbox `Firewall:` is preselected choosen~~ … tab `DNS` … tab `Confirm` … /dev/rbd0 Creating filesystem with 2097152 4k blocks and 524288 inodes Filesystem UUID: 39135f27-f6b8-4ecc-8b4d-abbe85a6df9d Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 extracting archive '/mnt/pve/cephfs/template/cache/nixos-21.05_2021-10-10.tar.xz' Total bytes read: 836218880 (798MiB, 28MiB/s) Architecture detection failed: open '/bin/sh' failed: No such file or directory Falling back to amd64. Use `pct set VMID --arch ARCH` to change. /etc/os-release file not found and autodetection failed, falling back to 'unmanaged' TASK OK (optional you can) check the (pve) lxc config file (and it should look like something like the following) `less /etc/pve/lxc/1000.conf` arch: amd64 cores: 1 features: nesting=1 hostname: CT1000 memory: 512 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=F6:CA:DB:A2:BF:B6,type=veth ostype: unmanaged rootfs: storage:vm-1000-disk-0,size=8G swap: 512 unprivileged: 1	`pct create` … ~~`pct create 1000 --arch amd64 --description nixos-template cephfs:vztmpl/nixos-21.05_2021-10-10.tar.xz --ostype unmanaged --net0 name=eth0 --storage storage --unprivileged 1`~~ (optional you can) check the (pve) lxc config file (and it should look like something like the following) `less /etc/pve/lxc/1000.conf` arch: amd64 hostname: CT1000 memory: 1024 net0: name=eth0 ostype: unmanaged rootfs: storage:vm-1000-disk-0,size=4G swap: 512 unprivileged: 1
customize the (pve) lxc startup setup routine (on every node where you want to start a NixOS container)		run_buffer: 316 Script exited with status 1 lxc_init: 816 Failed to run lxc.hook.pre-start for container "1000" __lxc_start: 2007 Failed to initialize container "1000" TASK ERROR: startup for container '1000' failed `nano /usr/share/perl5/PVE/LXC/Setup.pm` sub unified_cgroupv2_support { my ($self) = @_; return if !$self->{plugin}; # unmanaged $self->protected_call(sub { $self->{plugin}->unified_cgroupv2_support() }); } (after fixing all the other stuff) WARN: old systemd (< v232) detected, container won't run in a pure cgroupv2 environment! Please see documentation -> container -> cgroup version. TASK WARNINGS: 1	https://forum.proxmox.com/threads/92381/#post-402350
customize the individual Proxmox Virtual Environment container configuration for NixOS	sync_wait: 36 An error occurred in another process (expected sequence number 7) TASK ERROR: startup for container '1000' failed	sync_wait: 36 An error occurred in another process (expected sequence number 7) __lxc_start: 2073 Failed to spawn container "1000" TASK ERROR: startup for container '1000' failed editing the specific (pve) lxc config file (to a option for lxc.init.cmd) `nano /etc/pve/lxc/1000.conf` lxc.init.cmd: /init
(configure the available (virtual) network device for the Proxmox Virtual Environment container)
(activate nesting for NixOS in the Proxmox Virtual Environment container)		(optional you can) check the (pve) lxc config file (and it should look like something like the following with nesting=1 on the line features:) `less /etc/pve/lxc/1000.conf` arch: amd64 cores: 2 features: nesting=1 hostname: CT1000 memory: 1024 net0: name=eth0,bridge=vmbr0,hwaddr=A1:B2:C3:D4:E5:F6,ip=dhcp,type=veth ostype: unmanaged rootfs: storage:vm-1000-disk-0,size=4G swap: 512 unprivileged: 1
start the NixOS container with Proxmox Virtual Environment		`pct start` … ~~`pct start 1000`~~
login into the NixOS container	… (~~node~~(`Folder View`) `LXC Container` -> container) `Console` <<< Welcome to NixOS 21.05.3740.ce7a1190a0f (x86_64) - pts/0 >>> Log in as "root" with an empty password. nixos login: nixos login: root [root@nixos:~]#	`lxc-attach 1000` sh-4.4# sh-4.4# . /etc/profile [root@nixos:/]#
(optional) test rebuild of NixOS		(optional) check the default configuration file for NixOS `cat /etc/nixos/configuration.nix` { config, pkgs, ... }: { imports = [ <nixpkgs/nixos/modules/virtualisation/lxc-container.nix> ]; } `nixos-rebuild test` building Nix... building the system configuration... activating the configuration... setting up /etc... setting up tmpfiles warning: the following units failed: sys-kernel-debug.mount ● sys-kernel-debug.mount - Kernel Debug File System Loaded: loaded (/nix/store/n5j5fjn60nhck658j9ab84k8n9z24n1r-systemd-247.6/example/systemd/system/sys-kernel-debug.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2021-10-11 06:48:30 UTC; 265ms ago Where: /sys/kernel/debug What: debugfs Docs: https://www.kernel.org/doc/Documentation/filesystems/debugfs.txt https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems IP: 0B in, 0B out CPU: 2ms Oct 11 06:48:30 nixos systemd[1]: Mounting Kernel Debug File System... Oct 11 06:48:30 nixos mount[17997]: mount: /sys/kernel/debug: permission denied. Oct 11 06:48:30 nixos systemd[1]: sys-kernel-debug.mount: Mount process exited, code=exited, status=32/n/a Oct 11 06:48:30 nixos systemd[1]: sys-kernel-debug.mount: Failed with result 'exit-code'. Oct 11 06:48:30 nixos systemd[1]: Failed to mount Kernel Debug File System. warning: error(s) occurred while switching to the new configuration
fixing the configuration file for NixOS		(optional) check the default configuration file for NixOS `cat /etc/nixos/configuration.nix` { config, pkgs, ... }: { imports = [ <nixpkgs/nixos/modules/virtualisation/lxc-container.nix> ]; } `nano /etc/nixos/configuration.nix` { imports = [ <nixpkgs/nixos/modules/virtualisation/lxc-container.nix> ]; systemd.suppressedSystemUnits = [ "sys-kernel-debug.mount" ]; }	https://github.com/NixOS/nixpkgs/issues/9735#issuecomment-783535726
update the channel for NixOS (needed?)		`nix-channel --update`
…
…
…

Is there a need for non unprivileged NixOS containers?

Is there a scenario where you would like to have a privileged (unprivileged = 0) container?: I do not know.

Is there a cgroup2 only NixOS containers?

Is there a configuration with cgroups versions 2 only - where cgroups version 1 is not needed - (so that is possible to rollback the manipulation of the pve lxc startup script (/usr/share/perl5/PVE/LXC/Setup.pm))? Or can we create such a (pre)build image (tar)?: I do not know.

grep cgroup /proc/filesystems

nodev	cgroup
nodev	cgroup2

Notes

https://linuxcontainers.org/lxc/manpages//man5/lxc.container.conf.5.html

(pve) lxc configuration option lxc.cgroup2.devices.allow: a

(pve) lxc configuration option lxc.cgroup.devices.deny = a

https://wiki.debian.org/LXC/CGroupV2

https://search.nixos.org/options?channel=unstable&from=0&query=cgroup

https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Setup/Base.pm;h=a5b77d32f82747ea558d0398919414945b133dc0;hb=HEAD#l523

Talk:Proxmox Linux Container

NixOS container (LXC) on Proxmox Virtual Environment 7

Is there a need for non unprivileged NixOS containers?

Is there a cgroup2 only NixOS containers?

documentation