Install NixOS on Hetzner Online - Revision history

Klinger: Category:Deployment added

2024-10-26T09:13:36Z

← Older revision		Revision as of 09:13, 26 October 2024
Line 159:		Line 159:
	[[Category:Cookbook]]		[[Category:Cookbook]]
	[[Category:Server]]		[[Category:Server]]

			[[Category:Deployment]]

Gerg-L: updated networkd stuff to actually work on current nixos-unstable

2024-08-19T00:51:42Z

updated networkd stuff to actually work on current nixos-unstable

← Older revision		Revision as of 00:51, 19 August 2024
Line 18:		Line 18:
	systemd.network = {		systemd.network = {
	enable = true;		enable = true;
	networks.~~"30-wan"~~ = {		networks.default = {
	~~matchConfig.Name~~ = "enp1s0"; # The ~~predictable~~ name of the ~~network~~ interface		name = "enp1s0"; # The name of the interface
	~~networkConfig.~~DHCP = "ipv4";		DHCP = "ipv4";
	addresses = [		addresses = [
	# Replace the ~~subnet~~ with the one assigned to your machine		{
	"2a01:4f8:AAAA:BBBB::1/64"		# Replace the address with the one assigned to your machine
	];		Address = "2a01:4f8:AAAA:BBBB::1/64";
	~~gateway = [~~		}
	~~"fe80::1"~~
	];		];
			gateway = [ "fe80::1" ];
	linkConfig.RequiredForOnline = "routable";		linkConfig.RequiredForOnline = "routable";
	};		};
Line 40:		Line 40:
	enable = true;		enable = true;
	networks."30-wan" = {		networks."30-wan" = {
	~~matchConfig.Name~~ = "enp1s0"; # The predictable name of the network interface		name = "enp1s0"; # The predictable name of the network interface
	~~networkConfig.~~DHCP = "no";		DHCP = "no";
	addresses = [		addresses = [
	# Replace the ~~address and subnet~~ with the ~~one~~ assigned to your machine		# Replace the addresses with the ones assigned to your machine
	"A.B.C.D/26"		{
	~~# Replace the subnet with the one assigned to your machine~~		Address = "A.B.C.D/26";
	"2a01:4f8:AAAA:BBBB::1/64"		}
			{
			Address = "2a01:4f8:AAAA:BBBB::1/64";
			}
	];		];
	gateway = [		gateway = [

Hexa: /* Network configuration */

2024-06-09T21:17:24Z

Network configuration

← Older revision		Revision as of 21:17, 9 June 2024
Line 12:		Line 12:
	== Network configuration ==		== Network configuration ==

	Hetzner ~~Cloud~~ offers both IPv4 (usually in a shared /26 or /27 subnet) and IPv6 (/64 subnet) connectivity to each machine. The assigned addresses can be looked up on the [https://robot.hetzner.com/server Hetzner Robot] on the IPs tab of a machine. The public IPv4 address of the server can automatically be obtained via DHCP. For IPv6 you have to statically configure both address and gateway.		Hetzner Online offers both IPv4 (usually in a shared /26 or /27 subnet) and IPv6 (/64 subnet) connectivity to each machine. The assigned addresses can be looked up on the [https://robot.hetzner.com/server Hetzner Robot] on the IPs tab of a machine. The public IPv4 address of the server can automatically be obtained via DHCP. For IPv6 you have to statically configure both address and gateway.

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Hexa: /* Static IPv4 configuration */

2024-06-09T21:10:23Z

Static IPv4 configuration

← Older revision		Revision as of 21:10, 9 June 2024
Line 35:		Line 35:

	=== Static IPv4 configuration ===		=== Static IPv4 configuration ===
	Since the IPv4 network configuration is known, it can also be configured statically, preventing reliance on the DHCP service. The gateway and subnet information is visible when hovering the IPv4 address. The subnet size is usually a /26 (255.255.255.224) or a /27 (255.255.255.192).<syntaxhighlight lang="nix">		Since the IPv4 network configuration is known, it can also be configured statically, preventing reliance on the DHCP service. The gateway and subnet information is visible when hovering the IPv4 address. The subnet size is usually a /26 (<code>255.255.255.224</code>) or a /27 (<code>255.255.255.192</code>).<syntaxhighlight lang="nix">
	{		{
	systemd.network = {		systemd.network = {

Hexa: /* Network configuration */ IPV4 subnet is usually shared

2024-06-09T21:09:36Z

Network configuration: IPV4 subnet is usually shared

← Older revision		Revision as of 21:09, 9 June 2024
Line 12:		Line 12:
	== Network configuration ==		== Network configuration ==

	Hetzner Cloud offers both IPv4 (/32 or ~~shorter subnets~~) and IPv6 (/64 subnet) connectivity to each machine. The assigned addresses can be looked up on the [https://robot.hetzner.com/server Hetzner Robot] on the IPs tab of a machine. The public IPv4 address of the server can automatically be obtained via DHCP. For IPv6 you have to statically configure both address and gateway.		Hetzner Cloud offers both IPv4 (usually in a shared /26 or /27 subnet) and IPv6 (/64 subnet) connectivity to each machine. The assigned addresses can be looked up on the [https://robot.hetzner.com/server Hetzner Robot] on the IPs tab of a machine. The public IPv4 address of the server can automatically be obtained via DHCP. For IPv6 you have to statically configure both address and gateway.

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Hexa: /* Network configuration */ Bring in sync with Hetzner cloud and give only networkd examples for a static config, as well as one using DHCP

2024-06-09T21:08:15Z

Network configuration: Bring in sync with Hetzner cloud and give only networkd examples for a static config, as well as one using DHCP

← Older revision		Revision as of 21:08, 9 June 2024
Line 12:		Line 12:
	== Network configuration ==		== Network configuration ==

	~~From~~ Hetzner's [https://~~accounts~~.hetzner.com/~~login web interface~~]~~, one~~ can ~~obtain both ipv4/ipv6 addresses and gateways~~.		Hetzner Cloud offers both IPv4 (/32 or shorter subnets) and IPv6 (/64 subnet) connectivity to each machine. The assigned addresses can be looked up on the [https://robot.hetzner.com/server Hetzner Robot] on the IPs tab of a machine. The public IPv4 address of the server can automatically be obtained via DHCP. For IPv6 you have to statically configure both address and gateway.
	~~Hetzner does announce ipv6 addresses servers, so~~ you ~~need~~ to ~~assign those~~ statically.
	~~In this example, we use networkd to~~ configure ~~the interface. The same configuration can be used for~~ both
	~~the kexec installation image~~ and ~~the final server configuration~~.

	<~~syntaxHighlight~~ lang=nix>		<syntaxhighlight lang="nix">
	{ ~~... }: {~~		{
	~~# This make sure that our interface is named `eth0`.~~
	~~# This should be ok as long as you don't have multiple physical network cards~~
	~~# For multiple cards one could add a netdev unit to rename the interface based on the mac address~~
	~~networking.usePredictableInterfaceNames = false;~~
	systemd.network = {		systemd.network = {
	enable = true;		enable = true;
	networks."~~eth0~~"~~.extraConfig~~ = ''		networks."30-wan" = {
	~~[Match]~~		matchConfig.Name = "enp1s0"; # The predictable name of the network interface
	~~Name~~ = ~~eth0~~		networkConfig.DHCP = "ipv4";
	[~~Network]~~		addresses = [
	# ~~Add~~ your ~~own assigned ipv6 subnet here here!~~		# Replace the subnet with the one assigned to your machine
	~~Address =~~ 2a01:~~4f9~~:~~ffff~~::1/64		"2a01:4f8:AAAA:BBBB::1/64"
	~~Gateway~~ = fe80::1		];
	~~# optionally you can do the same for ipv4 and disable DHCP (networking.dhcpcd.enable = false~~;)		gateway = [
	~~# Address = 144.x.x~~.~~x/26~~		"fe80::1"
	~~# Gateway~~ = ~~144.x.x.1~~		];
	'';		linkConfig.RequiredForOnline = "routable";
			};
	};		};
	}		}
	</~~syntaxHighlight~~>		</syntaxhighlight>

	~~Another possibility~~ is ~~to use <code>networking~~.~~interfaces<~~/~~code>:~~		=== Static IPv4 configuration ===
	<~~syntaxHighlight~~ lang=nix>		Since the IPv4 network configuration is known, it can also be configured statically, preventing reliance on the DHCP service. The gateway and subnet information is visible when hovering the IPv4 address. The subnet size is usually a /26 (255.255.255.224) or a /27 (255.255.255.192).<syntaxhighlight lang="nix">
	~~let~~		{
	~~external-mac~~ = ~~"00:11:22:33:44:55";~~		systemd.network = {
	~~ext-if~~ = ~~"et0"~~;		enable = true;
	~~external-ip = "144.x.x~~.x";		networks."30-wan" = {
	~~external~~-~~gw =~~ "~~144.x.x.255";~~		matchConfig.Name = "enp1s0"; # The predictable name of the network interface
	~~external-ip6~~ = ~~"2a01:XXXX:XXXX::1";~~		networkConfig.DHCP = "no";
	~~external-gw6~~ = "~~fe80::1~~";		addresses = [
	~~external-netmask = 27;~~		# Replace the address and subnet with the one assigned to your machine
	~~external-netmask6 = 64;~~		"A.B.C.D/26"
	~~in {~~		# Replace the subnet with the one assigned to your machine
	# ~~rename the external interface based on the MAC~~ of the interface		"2a01:4f8:AAAA:BBBB::1/64"
	~~services.udev~~.~~extraRules = ''SUBSYSTEM=~~="~~net~~"~~, ATTR{address}=="${external-mac}", NAME="${ext-if}"''~~;		];
	~~networking = {~~		gateway = [
	~~interfaces."${ext-if}" = {~~		# Replace the gateway address with the one in your subnet
	~~ipv4.~~addresses = [{		"A.B.C.E"
	address ~~= external-ip;~~		"fe80::1"
	~~prefixLength = external-netmask;~~		];
	}];		linkConfig.RequiredForOnline = "routable";
	~~ipv6.addresses~~ = [{
	address ~~= external-ip6;~~
	~~prefixLength = external-netmask6;~~
	}];
	};
	~~defaultGateway6 = {~~
	~~address = external-gw6~~;
	~~interface~~ = ~~ext-if~~;
	};		};
	~~defaultGateway = external-gw;~~
	};		};
	}		}
	</~~syntaxHighlight~~>		</syntaxhighlight>

	== Bootstrap from the Rescue System ==		== Bootstrap from the Rescue System ==

imported>IgorM: Fixed syntax highlighting

2023-09-27T09:47:48Z

Fixed syntax highlighting

← Older revision		Revision as of 09:47, 27 September 2023
Line 157:		Line 157:

	At this point, edit the /mnt/etc/nixos/configuration.nix and tune as needed. I just added the following lines:		At this point, edit the /mnt/etc/nixos/configuration.nix and tune as needed. I just added the following lines:
	<syntaxHighlight>		<syntaxHighlight lang=nix>
	boot.loader.grub.device = "/dev/nvme0n1";		boot.loader.grub.device = "/dev/nvme0n1";
	services.openssh.enable = true;		services.openssh.enable = true;
Line 169:		Line 169:
	Voila! (after 1000 steps)		Voila! (after 1000 steps)

			[[Category:Cookbook]]
	[[Category:Server]]		[[Category:Server]]

imported>Nilsherzig at 10:28, 26 September 2023

2023-09-26T10:28:03Z

← Older revision		Revision as of 10:28, 26 September 2023
Line 5:		Line 5:
	There are three ways at the time to install NixOS on Hetzner dedicated:		There are three ways at the time to install NixOS on Hetzner dedicated:

	# From Hetzner's rescue image one can boot into the nixos installer using a custom kexec image that is configured with the fixed IPv6 provided by Hetzner and also contain your ssh key. Tip: The kexec tarball as generated by [https://github.com/nix-community/nixos-generators nixos-generators] can remain put into the /boot partition for future use.		# From Hetzner's rescue image, one can boot into the nixos installer using a custom kexec image that is configured with the fixed IPv6 provided by Hetzner and also contain your ssh key. Tip: The kexec tarball as generated by [https://github.com/nix-community/nixos-generators nixos-generators] can remain put into the /boot partition for future use.
	# Hetzner also provides an interface to upload your own ISO-images. Also here you may want to build your own iso-image, which has openssh with ssh keys due the lack of a remote console.		# Hetzner also provides an interface to upload your own ISO-images. Also, here you may want to build your own iso-image, which has openssh with ssh keys due the lack of a remote console.
	# An easier method to install NixOS on Hetzner, is to use the existing integration into NixOps.		# An easier method to install NixOS on Hetzner, is to use the existing integration into NixOps.
	# An example to install NixOS in the Hetzner rescue mode, including full RAID partitioning, is available [https://github.com/nix-community/nixos-install-scripts/blob/master/hosters/hetzner-dedicated/hetzner-dedicated-wipe-and-install-nixos.sh here].		# An example to install NixOS in the Hetzner rescue mode, including full RAID partitioning, is available [https://github.com/nix-community/nixos-install-scripts/blob/master/hosters/hetzner-dedicated/hetzner-dedicated-wipe-and-install-nixos.sh here].
Line 14:		Line 14:
	From Hetzner's [https://accounts.hetzner.com/login web interface], one can obtain both ipv4/ipv6 addresses and gateways.		From Hetzner's [https://accounts.hetzner.com/login web interface], one can obtain both ipv4/ipv6 addresses and gateways.
	Hetzner does announce ipv6 addresses servers, so you need to assign those statically.		Hetzner does announce ipv6 addresses servers, so you need to assign those statically.
	In this example we use networkd to configure the interface. The same configuration can be used for both		In this example, we use networkd to configure the interface. The same configuration can be used for both
	the kexec installation image and the final server configuration.		the kexec installation image and the final server configuration.

Line 88:		Line 88:

	First, reboot the machine in Rescue mode. Note that just enabling Rescue mode from the dashboard doesn't immediately reboot so make sure to power cycle the server. The Rescue mode runs from a RAM disk, so make also sure that you have enough RAM. Temporarily rescaling to 32 GiB of RAM (the RAM disk will be half of the available RAM) during the bootstrapping process helps. Make sure to select your SSH public key. SSH into the machine:		First, reboot the machine in Rescue mode. Note that just enabling Rescue mode from the dashboard doesn't immediately reboot so make sure to power cycle the server. The Rescue mode runs from a RAM disk, so make also sure that you have enough RAM. Temporarily rescaling to 32 GiB of RAM (the RAM disk will be half of the available RAM) during the bootstrapping process helps. Make sure to select your SSH public key. SSH into the machine:

			You can skip the entire next part by using https://github.com/nix-community/nixos-images#kexec-tarballs

	<syntaxHighlight lang=bash>		<syntaxHighlight lang=bash>
Line 123:		Line 125:
	</syntaxHighlight>		</syntaxHighlight>

	At this point the shell should stop responding. Kill the shell and ssh back into the machine. The server public key will have changed.		At this point, the shell should stop responding. Kill the shell and ssh back into the machine. The server public key will have changed.

	<syntaxHighlight lang=bash>		<syntaxHighlight lang=bash>
Line 135:		Line 137:

	# In this particular machine we have two NVMe disks		# In this particular machine we have two NVMe disks
			# If your machine has > 2TB drives, open a ticket and ask for UEFI boot, it will save you a lot of hassle
	format /dev/nvme0n1		format /dev/nvme0n1
	format /dev/nvme1n1		format /dev/nvme1n1

imported>Shyim: pin nixos-generator version

2023-09-14T17:41:12Z

pin nixos-generator version

← Older revision		Revision as of 17:41, 14 September 2023
Line 103:		Line 103:
	# Install nixos-generators		# Install nixos-generators
	# This might take a while, so the verbose flag `-v` is included to monitor progress		# This might take a while, so the verbose flag `-v` is included to monitor progress
	nix-env -f https://github.com/nix-community/nixos-generators/archive/~~master~~.tar.gz -i -v		nix-env -f https://github.com/nix-community/nixos-generators/archive/1.7.0.tar.gz -i -v

	# Create a initial config, just to kexec into		# Create a initial config, just to kexec into

imported>Golddranks: Turns out you need at least 16 GiB of disk space

2022-11-09T17:40:58Z

Turns out you need at least 16 GiB of disk space

← Older revision		Revision as of 17:40, 9 November 2022
Line 87:		Line 87:
	The main principle is that we will go from: Rescue system, install Nix, kexec into a NixOS system, finally install the system.		The main principle is that we will go from: Rescue system, install Nix, kexec into a NixOS system, finally install the system.

	First, reboot the machine in Rescue mode. Note that just enabling Rescue mode from the dashboard doesn't immediately reboot so make sure to power cycle the server. The Rescue mode runs from a RAM disk, so make also sure that you have enough RAM. Temporarily rescaling to ~~at least 16~~ GiB of RAM during the bootstrapping process ~~should help~~. Make sure to select your SSH public key. SSH into the machine:		First, reboot the machine in Rescue mode. Note that just enabling Rescue mode from the dashboard doesn't immediately reboot so make sure to power cycle the server. The Rescue mode runs from a RAM disk, so make also sure that you have enough RAM. Temporarily rescaling to 32 GiB of RAM (the RAM disk will be half of the available RAM) during the bootstrapping process helps. Make sure to select your SSH public key. SSH into the machine:

	<syntaxHighlight lang=bash>		<syntaxHighlight lang=bash>