Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
lub 06752d0d69 actually enable systemd-networkd il y a 2 jours
authorized_keys remove pandro from authorized_keys il y a 3 mois
config remove nftables il y a 2 jours
hardware add new ip addresses to hetzner network.sh il y a 4 semaines
README.md fix dropbear instructions in readme il y a 3 mois
post-debootstrap-installer.sh actually enable systemd-networkd il y a 2 jours
reset.sh remove -e from reset.sh il y a 3 mois
setup.sh use --bind instead of -o bind il y a 2 jours


These scripts setup a blank hardware server according to our requirements including partitions, raids, debootstrap, package installation and various other configuration. The goal is to create a server ready to join into the swarm.

Usage (from a live system):

# (!) wipes the start sectors of all disks (!)
# (!) review before executing (!)

./setup.sh <template> <fqdn>

# example:
./setup.sh ovh_rise-1 server321.example.com

# Unlock the disk after booting the server from disk:
# Dropbear is configured on 222 and only allows the user root
ssh -p 222 root@<fqdn>

setup.sh executes the hardware specific template files, debootstraps and invokes the actual installer inside the fresh environment.
As much as possible should be done in the chroot, as only there we have control over the software (the live system is normally provided by the hardware provider).

Templates (hardware/*) consist of three files:

  • esp - a symlink to the desired ESP partition
  • parted.sh - script to prepare the partitions. Should create ESP (/boot/efi), md0 (/) and md1 (/boot)
  • network.sh - creates the neccessary configs in /etc/systemd/network

config/* gets copied to the chroot and contains static config files

authorized_keys/* is used to create the users and populate their respective ~/.ssh/authorized_keys