Proxmox Linux Container: Difference between revisions

(14 intermediate revisions by 10 users not shown)

Line 1:

{{outdated|See [[Proxmox]] for instructions that apply to more recent versions of nixpkgs and proxmox.}}

= Building Proxmox Linux Containers with Nix =

You can use 'make-system-tarball' to create a Linux Container that can run on Proxmox, for example like https://codeberg.org/raboof/nix-mastodon-bot/src/branch/main/default.nix#L31

= NixOS =

With a small amount of work, it is possible to use NixOS as a LXC container under Proxmox.

== Generate a container tarball ==

A better way to deploy a NixOS container tarball on Proxmox is described at [[Proxmox Virtual Environment#LXC]].

== Finding a container tarball ==

~~First, choose a channel in~~ https://nixos.org/~~channels~~/~~. You will then~~ need ~~to either follow the via Hydra evaluation XXXX link~~, ~~or go to the URL listed in the <tt>src-url</tt> file~~.

Go to https://hydra.nixos.org/project/nixos, choose a release (small ones don't have the tarball we need), and open its Jobs tab.

On that page, search for nixos.containerTarball, open the link corresponding to your architecture (probably x86_64). Choose the latest success and click on the number. That is the ID of the result. Under Build products, download the system-tarball, which will be named <tt>nixos-system-x86_64-linux.tar.xz</tt>.

On that page, ~~use the search box to~~ search for containerTarball~~.x86_64~~. In the ~~results page, follow~~ the ~~link that~~ is the ID of the result. Under Build products, download the system-tarball, which will be named <tt>nixos-system-x86_64-linux.tar.xz</tt>.

Note the Build ID, it will be used when renaming the tarball... right when it's downloaded:

~~```~~

<pre>

mv nixos-system-x86_64-linux.tar.xz nixos-~~18.03~~-default_$~~BUILDID_amd64~~.tar.xz

mv nixos-system-x86_64-linux.tar.xz nixos-${RELEASE}-default_${BUILDID}_amd64.tar.xz

~~```~~

</pre>

This is a proxmox convention, and is useful to follow.

Line 23:

Line 33:

=== CLI operations ===

In the CLI, create a container ~~which will be used~~ as a template. I recommend setting a memorable ID.

In the CLI, create a container using the following command. If created as a template, I recommend setting a memorable ID.

<pre>

pct create 99999 \

--description nixos-template \

local:vztmpl/nixos-~~18.03~~-default_$~~BUILDID_amd64~~.tar.xz \

local:vztmpl/nixos-${RELEASE}-default_${BUILDID}_amd64.tar.xz \

-ostype unmanaged \

-net0 name=eth0 \

Line 39:

Line 49:

The last step using the CLI, edit <tt>/etc/pve/lxc/99999.conf</tt> to add this line:

<pre>

lxc.init.cmd: /sbin/init

</pre>

Before NixOS version 21.11 it was

<pre>

lxc.init.cmd: /init

</pre>

.

=== Creating a template ===

Line 49:

Line 64:

To create a new NixOS container, you can then clone the template instead of doing the preceding steps.

== Expected issues ==

=== Entering the container by <code>pct enter</code> ===

== ~~Expected issues~~ ==

enter a (nixos) container from the proxmox host

: <syntaxhighlight lang="shell">[root@proxmox:~]# pct enter <vmid></syntaxhighlight>

: <syntaxhighlight lang="shell">sh-5.2#</syntaxhighlight>

: <s>set (missing) environment variables</s>

:: <s><syntaxhighlight lang="shell">sh-5.2# source /etc/set-environment</syntaxhighlight></s>

:: <s><syntaxhighlight lang="shell">sh-5.2#</syntaxhighlight></s>

or

: set (missing) environment variables with <code>[[wikipedia:en:dot (command)#source|.]]</code>

:: <syntaxhighlight lang="shell">sh-5.2# . /etc/profile</syntaxhighlight>

:: <syntaxhighlight lang="bash">[root@nixos:~]#</syntaxhighlight>

If commands (like ls) still can't be found, try running:

:: <syntaxhighlight lang="shell">

[root@nixos:~] /run/current-system/activate

</syntaxhighlight>

<!--

or

: set (missing) environment variables by opening a new shell

:: <syntaxhighlight lang="shell">sh-5.2# sh -l</syntaxhighlight>

:: <syntaxhighlight lang="bash">[root@nixos:~]#</syntaxhighlight>

-->

=== nixos-rebuild switch ===

<code>nixos-rebuild switch</code> may fail with errors for special mount points. This does not look like it affects the container.

Line 70:

Line 108:

warning: error(s) occurred while switching to the new configuration

</pre>

=== Black Console in Proxmox ===

The Proxmox console may appear black when launched. It is at the login prompt but no existing text is rendered. Just type "root" and hit enter and new text will get rendered just fine. If you are still unable to get the console to render, you can try changing the console to `/dev/console` instead of the standard tty.

@@ Line 1: / Line 1: @@
+{{outdated|See [[Proxmox]] for instructions that apply to more recent versions of nixpkgs and proxmox.}}
+= Building Proxmox Linux Containers with Nix =
+You can use 'make-system-tarball' to create a Linux Container that can run on Proxmox, for example like https://codeberg.org/raboof/nix-mastodon-bot/src/branch/main/default.nix#L31
+= NixOS =
 With a small amount of work, it is possible to use NixOS as a LXC container under Proxmox.
+== Generate a container tarball ==
+A better way to deploy a NixOS container tarball on Proxmox is described at [[Proxmox Virtual Environment#LXC]].
 == Finding a container tarball ==
-First, choose a channel in https://nixos.org/channels/. You will then need to either follow the <em>via Hydra evaluation XXXX</em> link, or go to the URL listed in the <tt>src-url</tt> file.
+Go to https://hydra.nixos.org/project/nixos, choose a release (small ones don't have the tarball we need), and open its Jobs tab.
+On that page, search for <strong>nixos.containerTarball</strong>, open the link corresponding to your architecture (probably x86_64). Choose the latest success and click on the number. That is the ID of the result. Under <em>Build products</em>, download the <strong>system-tarball</strong>, which will be named <tt>nixos-system-x86_64-linux.tar.xz</tt>.
-On that page, use the search box to search for <strong>containerTarball.x86_64</strong>. In the results page, follow the link that is the ID of the result. Under <em>Build products</em>, download the <strong>system-tarball</strong>, which will be named <tt>nixos-system-x86_64-linux.tar.xz</tt>.
 Note the Build ID, it will be used when renaming the tarball... right when it's downloaded:
-```
+<pre>
-mv nixos-system-x86_64-linux.tar.xz nixos-18.03-default_$BUILDID_amd64.tar.xz
+mv nixos-system-x86_64-linux.tar.xz nixos-${RELEASE}-default_${BUILDID}_amd64.tar.xz
-```
+</pre>
 This is a proxmox convention, and is useful to follow.
@@ Line 23: / Line 33: @@
 === CLI operations ===
-In the CLI, create a container which will be used as a template. I recommend setting a memorable ID.
+In the CLI, create a container using the following command. If created as a template, I recommend setting a memorable ID.
 <pre>
 pct create 99999 \
    --description nixos-template \
-   local:vztmpl/nixos-18.03-default_$BUILDID_amd64.tar.xz \
+   local:vztmpl/nixos-${RELEASE}-default_${BUILDID}_amd64.tar.xz \
    -ostype unmanaged \
    -net0 name=eth0 \
@@ Line 39: / Line 49: @@
 The last step using the CLI, edit <tt>/etc/pve/lxc/99999.conf</tt> to add this line:
+<pre>
+lxc.init.cmd: /sbin/init
+</pre>
+Before NixOS version 21.11 it was
 <pre>
 lxc.init.cmd: /init
 </pre>
+.
 === Creating a template ===
@@ Line 49: / Line 64: @@
 To create a new NixOS container, you can then clone the template instead of doing the preceding steps.
+== Expected issues ==
+=== Entering the container by <code>pct enter</code> ===
-== Expected issues ==
+enter a (nixos) container from the proxmox host
+: <syntaxhighlight lang="shell">[root@proxmox:~]# pct enter <vmid></syntaxhighlight>
+: <syntaxhighlight lang="shell">sh-5.2#</syntaxhighlight>
+: <s>set (missing) environment variables</s>
+:: <s><syntaxhighlight lang="shell">sh-5.2# source /etc/set-environment</syntaxhighlight></s>
+:: <s><syntaxhighlight lang="shell">sh-5.2#</syntaxhighlight></s>
+or
+: set (missing) environment variables with <code>[[wikipedia:en:dot (command)#source|.]]</code>
+:: <syntaxhighlight lang="shell">sh-5.2# . /etc/profile</syntaxhighlight>
+:: <syntaxhighlight lang="bash">[root@nixos:~]#</syntaxhighlight>
+If commands (like ls) still can't be found, try running:
+:: <syntaxhighlight lang="shell">
+[root@nixos:~] /run/current-system/activate
+</syntaxhighlight>
+<!--
+or
+: set (missing) environment variables by opening a new shell
+:: <syntaxhighlight lang="shell">sh-5.2# sh -l</syntaxhighlight>
+:: <syntaxhighlight lang="bash">[root@nixos:~]#</syntaxhighlight>
+-->
+=== nixos-rebuild switch ===
 <code>nixos-rebuild switch</code> may fail with errors for special mount points. This does not look like it affects the container.
@@ Line 70: / Line 108: @@
 warning: error(s) occurred while switching to the new configuration
 </pre>
+=== Black Console in Proxmox ===
+The Proxmox console may appear black when launched. It is at the login prompt but no existing text is rendered. Just type "root" and hit enter and new text will get rendered just fine. If you are still unable to get the console to render, you can try changing the console to `/dev/console` instead of the standard tty.