sebdanielsson.dev

Analyze Boot Performance with systemd-analyze

Sebastian Danielsson — Mon, 18 Apr 2022 00:00:00 GMT

systemd comes with a tool for analyzing boot times, called systemd-analyze.

Update database

updatedb

Check current boot time

systemd-analyze time

systemd will show the boot time for the kernel, all of the user space processes and the total boot time.

List initialize time for all systemd units

systemd-analyze blame

Show start times for all processes. This helps you find bottlenecks in your boot process.

Create cloud-init templates in Proxmox

Sebastian Danielsson — Mon, 11 Jul 2022 00:00:00 GMT

Quickly deploy VMs in Proxmox VE with automated cloud-init templates. This guide covers creating, configuring, and using templates for fast, consistent provisioning.

Creating the template

Download an OpenStack compatible cloud image. For example Fedora Cloud Base 36.

wget https://download.fedoraproject.org/pub/fedora/linux/releases/37/Cloud/x86_64/images/Fedora-Cloud-Base-37-1.7.x86_64.qcow2

Set variables for STORAGE, IMAGE_FILE, TEMPLATE_ID, TEMPLATE_NAME, VM_ID, VM_NAME. Make sure these names and identifiers are unique.

STORAGE='local-lvm'
IMAGE_FILE='Fedora-Cloud-Base-37-1.7.x86_64.qcow2'
TEMPLATE_ID='1000'
TEMPLATE_NAME='fedora-template'
VM_ID='100'
VM_NAME='fedora-server'

Create a new VM to act as a template. Note: —ostype can be l26 for Linux kernel 2.6 or newer or win11 for Windows 11

qm create $TEMPLATE_ID --name $TEMPLATE_NAME --machine q35 --cpu cputype=host --core 2 --memory 2048 --net0 virtio,bridge=vmbr0 --bios ovmf --ostype l26

Add EFI disk.

qm set $TEMPLATE_ID -efidisk0 $STORAGE:0,format=raw,efitype=4m,pre-enrolled-keys=1

Add TPM Module (Only required for Windows 11.)

qm set $TEMPLATE_ID -tpmstate0 $STORAGE:1,version=v2.0

Import the downloaded image to local-lvm storage.

qm importdisk $TEMPLATE_ID $IMAGE_FILE $STORAGE

Attach our cloud-init image as a storage device.

qm set $TEMPLATE_ID --scsihw virtio-scsi-pci --scsi0 $STORAGE:vm-$TEMPLATE_ID-disk-1

Attach a drive for the cloud-init configuration.

qm set $TEMPLATE_ID --ide2 $STORAGE:cloudinit

Configure the VM to boot from our cloud-init image.

qm set $TEMPLATE_ID --boot c --bootdisk scsi0

Add a serial console for remote management with OpenStack.

qm set $TEMPLATE_ID --serial0 socket --vga serial0

Convert the VM into a VM template.

qm template $TEMPLATE_ID

Using the template

Clone the template into a new VM.

qm clone $TEMPLATE_ID $VM_ID --name $VM_NAME --full true

Resize the storage to your liking. New size can be new absolute size or prepend a + before the amount to add that amount storage in addition to current size.

qm resize $VM_ID scsi0 +20G

Add our public SSH key to the VM’s authorized_keys.

qm set $VM_ID --sshkey ~/.ssh/name_ed25519.pub

Configure the the username for the default user.

qm set $VM_ID --ciuser 'fedora'

Configure the the password for the default user.

qm set $VM_ID --cipassword 'SuperSecretPassword'

Start the newly created VM.

qm start $VM_ID

Run WireGuard & Transmission in a Docker Container

Sebastian Danielsson — Sat, 30 May 2020 00:00:00 GMT

Update 2021-05-23: This project is no longer maintained because there is a more clean way of achieving this with only a compose file. Check out my other repo here: SebDanielsson / compose-transmission-wireguard

I just released my first Docker image! It’s based on Alpine Linux and runs both WireGuard and Transmission in one container that weights in at about 30 MB. I’ve customized Transmission to run the excellent Secretmapper / combustion web interface and also applied my SebDanielsson / dark-combustion color palette.

GitHub: SebDanielsson / docker-wireguard-transmission
Docker Hub: sebdanielsson / wireguard-transmission

If you’re new to Docker you might want to check out my post “Get started with Docker”, covering the basic commands for administrating images, containers and docker-compose.

Usage

docker run

docker run --name wireguard-transmission \
--privileged \
-e "USERNAME=transmission" \
-e "PASSWORD=transmission" \
-e "INTERFACE=wg0" \
-e "KILLSWITCH=wg0" \
-p 51820:51820/udp \
-p 9091:9091 \
-v /path/to/wg-conf-dir:/etc/wireguard \
-v /path/to/transmission-conf-dir:/etc/transmission-daemon \
-v /path/to/transmission-complete-dir:/transmission/complete \
-v /path/to/transmission-incomplete-dir:/transmission/incomplete \
-v /path/to/transmission-watch-dir:/transmission/watch \
sebdanielsson/wireguard-transmission

docker-compose.yml

version: "3.7"
services:
wireguard-transmission:
container_name: wireguard-transmission
privileged: true
environment:
  - USERNAME=transmission
  - PASSWORD=transmission
  - INTERFACE=wg0
  - KILLSWITCH=wg0
ports:
  - "51820:51820/udp"
  - "9091:9091"
volumes:
  - "/path/to/wg-conf-dir:/etc/wireguard"
  - "/path/to/transmission-conf-dir:/etc/transmission-daemon"
  - "/path/to/transmission-complete-dir:/transmission/complete"
  - "/path/to/transmission-incomplete-dir:/transmission/incomplete"
  - "/path/to/transmission-watch-dir:/transmission/watch"
image: sebdanielsson/wireguard-transmission

Get started with Docker

Sebastian Danielsson — Sat, 30 May 2020 00:00:00 GMT

I just tried out Docker for a small project and now I get all the hype around it. While searching for good guides I stumbled upon this excellent tutorial by Prakhar Srivastav: A Docker Tutorial for Beginners. If you want a deeper understanding of Docker and how it works, and not only how to spin up a container and leave it running, I highly recommend reading it. He also go through the basics of writing your own Docker image which helped me a lot.

Documentation

Install

pacman -Syu docker docker-compose
systemctl start docker
systemctl enable docker
docker info

Usage

Function	Command
Pull image	docker pull `image`
Remove image	docker image rm `image`
List images	docker image ls
Run container	docker run —name `container` `options` `image`
List containers	docker container ls
Stop container	docker container stop `container`
Remove container	docker container rm `container`
Remove inactive containers	docker container prune
Switch to container shell	docker exec -ti `container` /bin/sh
Exit container shell	exit
Build image	docker build —no-cache -t `username`/`image`:`tag` .
Delete stopped containers, networks, images and build cache	docker system prune -a
Delete dangling volumes	docker volume prune
Rename volume	docker volume create —name `new_volume` && docker run —rm -it -v `old_volume`:/from -v `new_volume`:/to alpine ash -c “cd /from ; cp -av . /to” && docker volume rm `old_volume`

Docker Compose update images

If you’re using Docker compose and want to update the images to the latest versions you can run the following when in the same directroy as docker-compose.yaml

docker-compose up --force-recreate --build -d
docker image prune -f

Install Arch Linux

Sebastian Danielsson — Sat, 01 Feb 2020 00:00:00 GMT

This is my personal step-by-step guide for installing Arch Linux on x86-64 UEFI based machines. This guide is a slimmed down and simplified version of the Installation guide on ArchWiki.

Pre-installation

Keyboard layout

loadkeys sv-latin1

More info: console keymap

Pacman mirrors

Edit /etc/pacman.d/mirrorlist and uncomment a couple of nearby mirrors.

More info: mirrorlist

Verify the boot mode

ls /sys/firmware/efi/efivars

“Stuff” should show up.

More info: efivars

Test internet connection

ping -c 3 archlinux.org

More info: ping

Update the system clock

timedatectl set-ntp true

More info: timedatectl(1)

Create and format partitions

Find your drive

fdisk -l

More info: fdisk

Wipe the drive

shred --verbose --random-source=/dev/urandom --iterations=1 /dev/`yourdrive`

yourdrive should be replaced with your storage device, e.g. sda.

More info: shred

Create a boot and root partition

cfdisk /dev/`yourdrive`

More info: fdisk | cfdisk | partitioning

Partition table: GPT
New → Partition Size: 512 MiB → EFI System
New → Partition Size: xxxG → Linux Filesystem

List your partitions

fdisk -l `yourdrive`

Format the partitions

mkfs.fat -F32 /dev/`efipartition`
mkfs.ext4 /dev/`rootpartition`

More info: filesystems | mkfs.fat | mkfs.ext4

Mount the partitions

mount /dev/`rootpartition` /mnt
mkdir /mnt/boot
mount /dev/`efipartition` /mnt/boot

More info: mount

Installation

pacstrap /mnt base base-devel linux linux-firmware dhcpcd efibootmgr grub inetutils lvm2 man-db man-pages nano netctl sudo sysfsutils texinfo usbutils vi which

More info: pacstrap | base | base-devel

Configure the system

Fstab

genfstab -U /mnt >> /mnt/etc/fstab

More info: fstab

Chroot

This will change the root directory to our new installation.

arch-chroot /mnt

More info: chroot

Time

Set time zone

ln -sf /usr/share/zoneinfo/Europe/Stockholm /etc/localtime

More info: time zone

Set the hardware clock

hwclock --systohc --utc

More info: hwclock

Localization

Generate locales

Edit /etc/locale.gen and uncomment en_US.UTF-8 UTF-8.

locale-gen

More info: localizations

Set system language

LANG=en_US.UTF-8

More info: locale.conf

Set keyboard layout

For a Swedish keyboard layout, the file should contain: KEYMAP=sv-latin1.

KEYMAP=sv-latin1

More info: vconsole.conf

Network

Hostname

This file should only contain the hostname for this device

yourhostname

More info: hostname

Hosts

127.0.0.1 localhost
::1 localhost
127.0.1.1 myhostname.localdomain myhostname

Change hostname to your hostname
If this system has a public IP address, it should be used instead of 127.0.1.1

More info: hosts(5)

DHCP

To get network access we need to enable dhcpcd.service.

systemctl enable dhcpcd.service

More info: network managers | dhcpcd

Root password

passwd

More info: password

Bootloader

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub

More info: GRUB | UEFI | grub | efibootmgr

Microcode

Depending on your CPU you need to install the latest microcode.

pacman -S <intel-ucode or amd-ucode>

More info: Microcode | intel-ucode | amd-ucode

GRUB

grub-mkconfig -o /boot/grub/grub.cfg

More info: GRUB

Exit chroot

exit

Finish

Reboot

Reboot your system and remove your installation media.

reboot

Install Ghost with NGINX on Arch Linux

Sebastian Danielsson — Thu, 03 Feb 2022 00:00:00 GMT

Complete guide on how to install Ghost and using NGINX as a reverse proxy to make the site accessible on the internet over HTTP/2.

Installation

pacman -S nodejs-lts-fermium npm sqlite nginx-mainline certbot certbot-nginx
npm install ghost-cli@latest -g

Prepare directory

Create a directory to install Ghost to and cd to it

mkdir /var/www/`yourdomain.com`
cd /var/www/`yourdomain.com`

Install Ghost with a sqlite database

ghost install —-db=sqlite3

When asked about URL, enter the full URL to your domain. E.g. https://hogwarts.zone

Configuration

NGINX

DigitalOcean has provided a tool for configuring your web server over at nginxconfig.io, use it and follow the instructions to create a site. Then proceed with the instructions below.

Enable your site in NGINX

If you’ve generated a config as mentioned above you should be ready to activate your site.

cd /etc/nginx
ln -s sites-available/`yourdomain.com` sites-enabled/`yourdomain.com`

Disable the default site

If you want to disable the default site and create a new one, instead of adding your site to the default webroot, you can disable it by removing the symlink.

rm /etc/nginx/sites-enabled/default

Certificate renewal

Create a systemd service

[Unit]
Description=Let’s Encrypt renewal

[Service]
Type=oneshot
ExecStart=/usr/bin/certbot renew —quiet —agree-tos —deploy-hook “systemctl reload nginx.service”

Create a timer

Make it run twice a day at random times to help reduce load on Let’s Encrypt servers.

[Unit]
Description=Twice daily renewal of Let’s Encrypt’s certificates

[Timer]
OnCalendar=0/12:00:00
RandomizedDelaySec=1h
Persistent=true

[Install]
WantedBy=timers.target

Start and enable the service

systemctl start certbot.timer
systemctl enable certbot.timer

Run NGINX

systemctl start nginx
systemctl enable nginx

Live

Your website should now be live at https://yourdomain.com.

Install NGINX on Arch Linux

Sebastian Danielsson — Tue, 04 Feb 2020 00:00:00 GMT

Fast and easy tutorial for installing a NGINX web server with HTTP/2 and TLS certificates from Let’s Encrypt on Arch Linux.

Installation

pacman -S nginx-mainline certbot certbot-nginx

The default page served at http://127.0.0.1 is located at /usr/share/nginx/html/index.html.

Configuration

DigitalOcean has provided a tool for configuring your web server over at nginxconfig.io, use it and follow the instructions to create a site. Then proceed with the instructions below.

Disable the default site

If you want to disable the default site and create a new one, instead of adding your site to the default webroot, you can disable it by removing the symlink.

rm /etc/nginx/sites-enabled/default

Automatically renew the certificates

Create a systemd service

[Unit]
Description=Let’s Encrypt renewal

[Service]
Type=oneshot
ExecStart=/usr/bin/certbot renew —quiet —agree-tos —deploy-hook “systemctl reload nginx.service”

Create a timer

Make it run twice a day at random times to help reduce load on Let’s Encrypt servers

[Unit]
Description=Twice daily renewal of Let’s Encrypt’s certificates

[Timer]
OnCalendar=0/12:00:00
RandomizedDelaySec=1h
Persistent=true

[Install]
WantedBy=timers.target

Start and enable the service

systemctl start certbot.timer
systemctl enable certbot.timer

Run NGINX

systemctl start nginx
systemctl enable nginx

Live

Your website should now be live at https://yourdomain.com.

Install paru on Arch Linux

Sebastian Danielsson — Tue, 18 May 2021 00:00:00 GMT

Paru is the newest and hottest AUR Helper. From one of the developers of yay and written is Rust this project has gained a lot of traction in the Arch commuinty. This guide will walk you through the steps for installing this AUR Helper which lets you install packages from the AUR (Arch User Repository) in the same way you install packages from the Arch repos with pacman.

Read more: paru - GitHub

Installation

pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si

Usage

Command	Function
paru -Ss foo	Searches for package foo on the repos or the AUR.
paru -Si foo	Get information about a package.
paru -S foo	Installs package foo from the repos or the AUR.
paru -d foo	Remove a package from the local repo.
paru -Syu	Update package list and upgrade all installed repo and AUR packages.
paru -Sua	Update all currently installed AUR packages.
paru -Qua	Print available AUR updates.
paru -c	Uninstall unneeded dependencies.

Install Phoronix Test Suite on Arch Linux

Sebastian Danielsson — Sat, 29 Feb 2020 00:00:00 GMT

This guide will walk through the steps for installing the Phoronix Test Suite on Arch Linux. The software will be installed from the Arch User Repository (AUR) with the help of the AUR Helperyay. If you don’t have an AUR Helper you should definately install one. I have a guide for two of them: Install yay on Arch Linux & Install paru on Arch Linux.

Phoronix Test Suite - Documentation

Installation

paru -S phoronix-test-suite

Usage

Function	Command
List tests	phoronix-test-suite list-tests
Install test	phoronix-test-suite install `test`
Run test	phoronix-test-suite run `test`

Install Reflector on Arch Linux

Sebastian Danielsson — Sun, 29 Mar 2020 00:00:00 GMT

Reflector is a small Python3 script that sort through the Arch Linux mirrors based on parameters of your choice and updates your mirrorlist.

More info: Reflector - ArchWiki | Project website - xyne

Installation

pacman -S reflector

Usage

reflector --help will show you the available commands and their options.

The following command will update your mirrorlist with the 50 fastest mirrors that have support for both HTTPS and IPV6.

reflector --verbose --completion-percent 100 --ipv6 --protocol https --score 50 --sort rate --save /etc/pacman.d/mirrorlist

Service

Reflector can run automatically in the background at chosen intervalls. The default timer will run reflector once a week.

If you want the options from the example earlier make the following changes.

--save /etc/pacman.d/mirrorlist
--completion-percent 100
--protocol https
--ipv6
--score 50
--sort rate

systemctl enable reflector.timer
systemctl start reflector.timer
systemctl start reflector.service

Install tmux on Arch Linux

Sebastian Danielsson — Thu, 11 Feb 2021 00:00:00 GMT

Tmux is a terminal multiplexer. This lets you to run multiple terminal sessions simultaniously. It gives you multitasking capabilities for your terminal and more importantly, this enables you to complete system updates even after a broken SSH connection since terminal sessions can be resumed.

Read more: tmux(1)

Installation

pacman -S tmux

Sane scrolling

The default scrolling behaviour runs through the previous commands instead of scrolling the terminal output. Enable sane scrolling behaviour with this config line.

set -g mouse on

Usage

Commands

Here is a summary of the most common commands that you’ll want to use.

Command	Function
tmux	Start a new session
tmux new -s `name`	Start a new named session
tmux ls	List sessions
tmux attach	Attach to the most recently used session
tmux attach -t `name`	Attach to a named session
tmux kill-session -t `name`	Kill a named session

Key bindings

Tmux also have a lot of keybindings to help you manage all sessions and windows. Here are the essential bindings that you’ll want to learn. The default key combination to initiate a command is Ctrl+b / control+b.

Command	Function
Ctrl+b ?	List all key bindings.
Ctrl-b d	Detach from the current session
Ctrl+b %	Add a new pane to the right
Ctrl+b “	Add a new pane to the bottom
Ctrl+b %	Split pane horizontally
Ctrl+b “	Split pane vertically
Ctrl+b o	Switch to the next pane
Ctrl+b ;	Move between the current and previous pane
Ctrl+b `arrow-key`	Navigate between the panes
Ctrl+b x	Ctrl+b x Close the current pane
Ctrl-b c	Create a new window
Ctrl-b w	Switch between sessions and windows

Install Transmission on Arch Linux

Sebastian Danielsson — Mon, 03 Feb 2020 00:00:00 GMT

This guide show you how to install Transmission on Arch Linux and configure it with a kill switch so that Transmission will only download and upload using a specific IP address. For example a WireGuard VPN. The guide is based on the tutorial over at the Transmission Wiki on GitHub. Documentation for the config file can be found over at the GitHub Wiki page as well.

Installation

pacman -S transmission-cli

Configuration

Generate config file**

systemctl start transmission.service
systemctl stop transmission.service

Edit the config file**

Make sure Transmission is not running when making changes to this file, otherwise the changes won’t save.
The last line shall not end with a comma!
Change webuiusername and webuipassword. When Transmission run the password will be encrypted. Depending on your subnetting for your VPN and LAN you might need to change the values in rpc-whitelist. In my config I set umask: 2, (base 10) which is the same as umask 002 and octal 775. octal to umask Calculator | octal to base 10 converter
If you want a kill switch, enter your local VPN IP on line ”bind-address-ipv4”: ”*.*.*.*”,. Transmission will only download/upload through this IP. If the VPN connection is dropped Transmission will stop all traffic.
Below are my recommended changes.

”encryption”: 1,
”dht-enabled”: false,
”lpd-enabled”: false,
”pex-enabled”: false,
”port-forwarding-enabled”: false,
”rpc-username”: ”<webuiusername>”,
”rpc-password”: ”<webuipassword>”,
”rpc-url”: ”/transmission/”,
”rpc-whitelist”: ”127.0.0.1,192.168.*.*”,
”umask”: 2,
”utp-enabled”: false

Change the WebUI theme

To change theme of the web UI, change the default web root to a directory that the user that’s running transmission can access. Add the following environmental variable.

[Service]
Environment=TRANSMISSION_WEB_HOME=/usr/share/transmission

Put the theme into the folder that you pointed to and you should be all set.

Reload services

systemctl daemon-reload

Checking for errors and testing

systemctl start transmission.service
systemctl status transmission.service

Enable autostart

systemctl start transmission.service
systemctl enable transmission.service

Bonus

You can make Transmission Web UI remotely accessible by either connecting to your LAN with WireGuard or by making the Web UI accessible on the internet over HTTPS with NGINX reverse proxy.

Install WireGuard [Client] on Arch Linux

Sebastian Danielsson — Mon, 03 Feb 2020 00:00:00 GMT

This is a very basic tutorial on how to install WireGuard on Arch Linux to use it as a VPN client. For example if you need maximum privacy while torrenting your favorite Linux distros.

Installation

pacman -S wireguard-tools

Configuration

Generate keys

First up we need to generate our private and public key. The private key should reside in our configuration and the public key will be used by the other peers, in this case the server. If you have already been provided with a complete config file you can skip to the next section. Remember that you and the server and are not supposed to know each other’s private key. You only need to exchange the public keys.

wg genkey | tee privatekey | wg pubkey > publickey

Print the keys and copy them for the following configuration.

cat peer1-privatekey && cat peer1-publickey

Configure your first tunnel

In this tutorial we’ll use wg0 as the name for our WireGuard interface. If you already have a WireGuard configuration named wg0, make sure to use another name for this configuration.

Below is an example config for routing all traffic except local (192.168.1.*) through the VPN. If your local subnet is on e.g. 192.168.0.X

[Interface]
PrivateKey = `PRIVATEKEY`
Address = `IPV4FROMVPNPROVIDER`,`IPV6FROMVPNPROVIDER`
DNS = `VPNDNS4`,`VPNDNS6`
PostUp = ip route add `192.168.1.0/24 via 192.168.1.1`;
PreDown = ip route delete `192.168.1.0/24`;

[Peer]
PublicKey = `PUBLICKEY`
AllowedIPs = `0.0.0.0/0`,`::0/0`
Endpoint = `PUBLICVPNSERVERIP`:`PORT`
PersistentKeepalive = 25

Starting WireGuard

Manually bring up the WireGuard interface and check for any errors.

systemctl start wg-quick@wg0
systemctl status wg-quick@wg0

You may want to bring up the interface automatically as a service with systemd.

systemctl enable wg-quick@wg0

Install WireGuard [Server] on Arch Linux

Sebastian Danielsson — Wed, 05 Feb 2020 00:00:00 GMT

This is a very basic tutorial on how to install WireGuard on Arch Linux to use it as a VPN server. For example if you want to access your home LAN from remote locations.

Installation

pacman -S wireguard-tools

Configuration

In this tutorial we’ll use wg0 as the name for our WireGuard interface. If you already have a WireGuard configuration named wg0, make sure to use another name for this configuration.

Server configuration

Generate server keys

First up we need to generate our private and public key. The private key should reside in our configuration and the public key will be used by the peers.

wg genkey | tee server1-privatekey | wg pubkey > server1-publickey

Print the keys and copy them for the following configuration.

cat server1-privatekey && cat server1-publickey

[Interface]
PrivateKey = <SERVER_PRIVATE_KEY>
Address = 10.0.2.1/24
ListenPort = 51820
# IF SERVER IS BEHIND NAT YOU WILL NEED THE FOLLOWING TWO RULES, ASSUMING YOUR ETHERNET ADAPTER IS NAMED "eth0" OTHERWISE CHANGE TO MATCH YOUR NAME
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

# Peer1
[Peer]
PublicKey = <PEER1_PUBLIC_KEY>
PresharedKey = <PEER1_PRE-SHARED-KEY_(OPTIONAL)>
AllowedIPs = 10.0.2.2/32

# Peer2
[Peer]
PublicKey = <PEER2_PUBLIC_KEY>
AllowedIPs = 10.0.2.3/32

Peer configuration

Peers will need to geneate a private and public key as well. Remember that you and the server and are not supposed to know each other’s private key. You only need to exchange the public keys. Generate a private and public key for each peer.

wg genkey | tee peer1-privatekey | wg pubkey > peer1-publickey

Peer1 config

Print the keys and copy them for the following configuration.

cat peer1-privatekey && cat peer1-publickey

[Interface]
PrivateKey = <PEER1_PRIVATE_KEY>
Address = 10.0.2.2/32
DNS = 1.1.1.1

[Peer]
PublicKey = <SERVER_PUBLICKEY>
PresharedKey = <PRE-SHARED-KEY_OPTIONAL>
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = <SERVER-HOSTNAME-OR-IP>:51820
PersistentKeepalive = 25

Peer2 config

Print the keys and copy them for the following configuration.

cat peer2-privatekey && cat peer2-publickey

[Interface]
PrivateKey = <PEER2_PRIVATE_KEY>
Address = 10.0.2.3/32
DNS = 1.1.1.1

[Peer]
PublicKey = <SERVER_PUBLICKEY>
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = <SERVER-HOSTNAME-OR-IP>:51820
PersistentKeepalive = 25

For a computer, share the respective peer config file to the user, e.g. with magic-wormhole. If they are a mobile user you might want to use qrencode and let them scan a QR code. cd to the directory containing the peer config files and generate the QR codes.

qrencode -t ansiutf8 < wg0-peer1.conf
qrencode -t ansiutf8 < wg0-peer2.conf

Enable IPv4 forwarding

sysctl -w net.ipv4.ip_forward=1

Make the change permanent:

net.ipv4.ip_forward = 1

Starting WireGuard

Manually bring up the WireGuard interface and check for any errors.

systemctl start wg-quick@wg0
systemctl status wg-quick@wg0

You may want to bring up the interface automatically as a service with systemd.

systemctl enable wg-quick@wg0

Install yay on Arch Linux

Sebastian Danielsson — Thu, 27 Feb 2020 00:00:00 GMT

This guide will walk through the steps for installing yay (Yet another Yogurt) which is an AUR Helper. This will let you install packages from the AUR (Arch User Repository) in the same way you install packages from the Arch Repo with pacman.

Update 2021-05-21: There is a new AUR Helper that has got a lot of traction. It’s called paru and works mostly the same but is written in Rust! I have a guide for installing it as well.

yay - GitHub

Installation

Do not run makepkg -si as root.

pacman -S git binutils make gcc fakeroot
git clone https://aur.archlinux.org/yay-bin.git
cd yay-bin
makepkg -si

Usage

Command	Function
yay -Ss foo	Searches for package foo on the repos or the AUR.
yay -Si foo	Get information about a package.
yay -S foo	Installs package foo from the repos or the AUR.
yay -Rns foo	Remove package, its dependencies and config files.
yay -Syu	Update package list and upgrade all installed repo and AUR packages.
yay -Sua	Update all currently installed AUR packages.
yay -Qua	Print available AUR updates.
yay -Yc	Uninstall unneeded dependencies.

Start a Minecraft Bedrock Server using Docker

Sebastian Danielsson — Thu, 10 Sep 2020 00:00:00 GMT

This guide will show you how to start a Minecraft Bedrock dedicated server using Docker.

Preparations

Docker volume

Create a Docker volume where we will store our server.

docker volume create minecraft

docker-compose.yaml

services:
  minecraft:
    container_name: "minecraft"
    image: itzg/minecraft-bedrock-server
    ports:
      - "19132:19132/udp"
    volumes:
      - "minecraft:/data"
    environment:
      EULA: "TRUE"
      SERVER_NAME: "Minecraft Server"
      SERVER_PORT: "19132"
      GAMEMODE: "survival"
      DIFFICULTY: "easy"
      LEVEL_TYPE: "DEFAULT"
      ALLOW_CHEATS: "true"
      MAX_PLAYERS: "10"
      ONLINE_MODE: "true"
      #WHITE_LIST: ""
      VIEW_DISTANCE: "12"
      TICK_DISTANCE: "12"
      PLAYER_IDLE_TIMEOUT: "0"
      MAX_THREADS: "8"
      LEVEL_NAME: "level"
      #LEVEL_SEED: ""
      DEFAULT_PLAYER_PERMISSION_LEVEL: "member"
      TEXTUREPACK_REQUIRED: "false"
      SERVER_AUTHORITATIVE_MOVEMENT: "true"
      PLAYER_MOVEMENT_SCORE_THRESHOLD: "20"
      PLAYER_MOVEMENT_DISTANCE_THRESHOLD: "0.3"
      PLAYER_MOVEMENT_DURATION_THRESHOLD_IN_MS: "500"
      CORRECT_PLAYER_MOVEMENT: "false"
volumes:
  minecraft:
    external:
      name: minecraft

server.properties

This Docker Image gives you a bunch of environment variables to configure the server.properties config file. Check out this wiki page describing all server properties.

permissions.json

There are three roles: operator, member, visitor. Players are defined by their unique xuid (Xbox User ID) in decimal. You can find players xuid by entering their Xbox Live Gamertag and checking the decimal button on this site: https://cxkes.me/xbox/xuid

After running the container for the first time you should be able to find permissions.json at /var/lib/docker/volumes/minecraft/_data/permissions.json if you named your volume minecraft.

Example

[
  {
    "permission": "operator",
    "xuid": "451298348"
  },
  {
    "permission": "member",
    "xuid": "52819329"
  },
  {
    "permission": "visitor",
    "xuid": "234114123"
  }
]

Start

docker-compose up -d