Arch Linux Server Administration Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

Where Arch Linux sits

Arch Linux is a rolling distribution. pacman -Syu upgrades the system to the current packages. There is no old point release to stay on. That is a good lab and a demanding server. Someone has to read the news before a full upgrade, because a manual intervention note is normal here and rare on Debian stable.

The installer is deliberate. You partition, you bootstrap, you configure the bootloader. The provisioning guide's idea still holds: the notes you used are the file you keep. A host built from memory cannot be rebuilt at 2 a.m.

systemd is the init. The systemd guide applies. The network might be systemd-networkd or NetworkManager depending on what you installed. Look. The lab address 192.0.2.10/24 is documentation. There is no default firewall product until you install one. Decide, then allow the management prefix, not the world.

Keyring trouble is solved by updating archlinux-keyring the way the Arch news describes, not by disabling signature checks. A host that skips signatures is not a hardened host.

The first hour on a lab host

Step 1 on Arch Linux covers the model. Write that this host is rolling and name the person who reads upgrade news. Without that person, pick a different distribution. The check is: The name is in the ticket. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Arch Linux draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 2 on Arch Linux covers admin and boot. Confirm the bootloader, the hostname edge-01, and a named user with a key. An Arch install is easy to leave without a bootloader check. The check is: A reboot comes back, and the key works. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Arch Linux draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 3 on Arch Linux covers network. Identify systemd-networkd or NetworkManager and set the lab address with that tool. Arch does not pick one for you. The check is: The address survives reboot. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Arch Linux draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 4 on Arch Linux covers firewall choice. Install the firewall you chose and allow the management prefix only. No firewall is a decision you write, not an omission. The check is: The decision is a sentence, and a test from outside the prefix fails if a firewall is on. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Arch Linux draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

Step 5 on Arch Linux covers a full upgrade. pacman -Syu after reading the news, on the lab host, with console open. A partial upgrade is the mistake. The check is: The transaction completed and the host reboots. If that check fails, stop and fix the ticket before the next step. The way back is the previous file or the previous image, which the provisioning guide told you to keep. Do not install a second package to hide a failed step. The browser generators for Arch Linux draft a starter. They do not log in. Read the draft, delete what this lab does not need, and replace prompt-for-this. A line that worked on a different distribution is not a reason to paste it here.

# Arch Linux lab. Review before you paste.
# Rolling. Read news before pacman -Syu.
# Do not disable signature checks.
# Lab address 192.0.2.10/24 via 192.0.2.1.
# prompt-for-this is not a password to keep.
# The AUR is out of scope for the first hour.

The commands you will actually repeat

Full upgrades on a cadence you chose, after reading the news for manual steps. Partial upgrades are how Arch breaks. Do not pacman -Sy and then install one package against old libraries.

The patch guide's canary matters more here, not less, because the delta can be large.

A server on Arch needs the same backup and console as any other host, plus a person who accepts the rolling model in writing.

The AUR is user-produced content. It is not the distribution. Adding an AUR helper on a server is a decision with an owner, not a step in the first hour.

What Arch Linux is not

Arch is not a set-and-forget server.

It is not Debian, Fedora, or RHEL. Their package commands do not belong.

Disabling signature checks is not a fix. The keyring update is the fix.

The hour you stop

Write the hostname, the role, and the clock time before you change Arch Linux. If this host is also serving users, it is not the lab and this first hour belongs on a spare. The provisioning guide is how the spare gets built. A change without a spare is a change you can still postpone.

Keep the console or the out-of-band path open for the whole hour. Reloading a network service, a firewall, or a secure-shell daemon from the only session is how a lab becomes a drive across town. The hardware guide names that path for a physical machine. A virtual machine uses the hypervisor console. A cloud instance uses the serial console the platform gives you. Test it before the reload, not after.

The address 192.0.2.10/24 and the gateway 192.0.2.1 are documentation. They belong in the lab note and nowhere else. On a real network, use the prefix the network desk already assigned. On a cloud instance, use the address the platform assigned and do not hard-code the documentation range into user-data. If a generator filled the documentation address into a production draft, delete it.

prompt-for-this is a reminder that a secret is missing. It is not a password you set, not a token you commit, and not a string you leave in a configuration file because the service started. The real secret lives in the password store. The ticket says who can read it. A file that still contains the reminder is a file you have not finished.

One service is enough for the first hour on Arch Linux. The purpose from the fundamentals page says which service. Every other package stays uninstalled until its own guide has a ticket. A host that enables a web server, a database, and a queue in the first hour has three changes and no proof. Finish the login, the address, and the update. Then stop.

Read the package transaction before you accept it. A count of packages is not a review. If the list contains a repository you did not add, stop. If it contains a kernel, the patch guide's reboot decision applies and the console stays open. If it contains software this role does not need, remove that line from the plan rather than installing it and disabling it later.

The previous image, the previous configuration file, or the previous package version is the rollback. Write the path down while the host still works. A rollback you invent after a failed reload is a guess. The migration guide assumes the old copy is still there. Do not delete it in the same hour to free a disk.

When the checks pass, copy the notes into the ticket and leave the host alone. The next host waits until a second person can repeat the login and the address from the notes. A fleet built from memory drifts. A fleet built from the file the provisioning guide stored stays boring, which is the point of Arch Linux in production.

If a step on Arch Linux fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a host nobody can rebuild. Rebuild from the image instead. The time you lose is smaller than the time you will spend explaining the hybrid.

Hand the finished lab to the guide that matches the role: web, mail, storage, backup, or hardening. Arch Linux being installed is not the same as the role being ready. The role guide has its own proof. Do not skip it because the package manager exited without an error.

A second person reads the hostname, the address, and the rollback path aloud before you build the next host. If they cannot find those three in the ticket, the notes are not done. Silence is not agreement. The check is the sentence they repeat back.

Store the working notes next to the image version. A month from now Arch Linux will still boot from that pair, and the chat where you remembered a flag will be gone. The file is the memory. The host is replaceable. That is the whole point of writing this hour down.

Arch Linux checks before a second host

Confirm this before you call the change done: Arch Linux is the OS the hostname reports, not a neighbour you copied from. The lab address 192.0.2.10/24 is gone before this host is placed on a real network. prompt-for-this is not the password that was set, and no password is in the ticket. The named admin can log in with a key. The package manager used is the one this page names. A network file from a different distribution was not pasted in. The config test or the apply command for this network tool succeeded. The previous image or install file is kept. No new third-party repository was added in the first hour. A service you do not need was not enabled to see what it does. Console or out-of-band access works before you reload SSH. A second person read the hostname and the address. Signature checks are still on. The upgrade owner is named. No AUR package is required for the base host. And a reboot after the first full upgrade succeeded. If one of those fails, stop.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Guides in this cluster

These supporting pages belong to this pillar.