Alpine Linux Installation on Raspberry Pi | Minimal, efficient containerization on ARM hardware

August 2023 16 min read

Docs • Linux • Tutorial

This guide walks through installing Alpine Linux on a Raspberry Pi 4, from image flashing through to a secure, containerized system ready for workloads. It covers a practical five-stage installation workflow, including ARM-specific bootloader and filesystem configuration required for reliable boots. The result is a minimal base system with Docker, SSH hardening, firewall rules, and static networking configured.

Alpine Linux Installation on Raspberry Pi

<details id="toc-wrapper" style="border: 1px solid var(--primary-color, #444444); padding: 0.75rem 1rem; margin: 1rem 0; border-radius: 0.25em;"> <summary style="cursor: pointer; font-weight: 600;">Table of Contents</summary> <nav id="TOC" role="doc-toc" style="margin-top: 0.75rem; text-align: left;"> <ul> <li><a href="#why-alpine-on-raspberry-pi" id="toc-why-alpine-on-raspberry-pi"><span class="toc-section-number">1</span> Why Alpine on Raspberry Pi</a></li> <li><a href="#prerequisites" id="toc-prerequisites"><span class="toc-section-number">2</span> Prerequisites</a></li> <li><a href="#installation-workflow" id="toc-installation-workflow"><span class="toc-section-number">3</span> Installation Workflow</a> <ul> <li><a href="#initial-setup" id="toc-initial-setup"><span class="toc-section-number">3.1</span> Initial Setup</a></li> <li><a href="#partitioning" id="toc-partitioning"><span class="toc-section-number">3.2</span> Partitioning</a></li> <li><a href="#boot-restructure" id="toc-boot-restructure"><span class="toc-section-number">3.3</span> Boot Restructure</a></li> <li><a href="#fstab-configuration" id="toc-fstab-configuration"><span class="toc-section-number">3.4</span> fstab Configuration</a></li> <li><a href="#users-and-packages" id="toc-users-and-packages"><span class="toc-section-number">3.5</span> Users and Packages</a></li> </ul></li> <li><a href="#first-boot-and-verification" id="toc-first-boot-and-verification"><span class="toc-section-number">4</span> First Boot and Verification</a></li> <li><a href="#networking-and-security" id="toc-networking-and-security"><span class="toc-section-number">5</span> Networking and Security</a> <ul> <li><a href="#static-ip-configuration" id="toc-static-ip-configuration"><span class="toc-section-number">5.1</span> Static IP Configuration</a></li> <li><a href="#firewall" id="toc-firewall"><span class="toc-section-number">5.2</span> Firewall</a></li> <li><a href="#ssh-key-authentication" id="toc-ssh-key-authentication"><span class="toc-section-number">5.3</span> SSH Key Authentication</a></li> </ul></li> <li><a href="#system-updates" id="toc-system-updates"><span class="toc-section-number">6</span> System Updates</a></li> <li><a href="#docker-and-container-management" id="toc-docker-and-container-management"><span class="toc-section-number">7</span> Docker and Container Management</a></li> <li><a href="#common-gotchas" id="toc-common-gotchas"><span class="toc-section-number">8</span> Common Gotchas</a></li> <li><a href="#next-steps" id="toc-next-steps"><span class="toc-section-number">9</span> Next Steps</a></li> <li><a href="#verification-checklist" id="toc-verification-checklist"><span class="toc-section-number">10</span> Verification Checklist</a></li> </ul> </nav> </details> <h1 data-number="1" id="why-alpine-on-raspberry-pi"><span class="header-section-number">1</span> Why Alpine on Raspberry Pi</h1> <p>Alpine Linux runs exceptionally well on ARM hardware because it aligns with ARM’s design philosophy: minimal instruction sets, low power consumption, and resource efficiency. Alpine’s userspace mirrors this approach: busybox instead of GNU coreutils, musl instead of glibc.</p> <p>In practice, a 4GB Raspberry Pi 4 runs Alpine with minimal overhead. The kernel uses roughly 70MB of RAM, Alpine’s userland adds only a few MB more, and you’re left with substantial headroom for Docker containers and services. This efficiency justifies the tradeoff of incompatibility with some x86-centric software.</p> <p>Alpine’s official Raspberry Pi images are well-maintained and ship with bootloader and kernel optimizations pre-configured. However, the installation process differs from Debian/Ubuntu approaches, so understanding the process prevents surprises later.</p> <h1 data-number="2" id="prerequisites"><span class="header-section-number">2</span> Prerequisites</h1> <p>You need: - Raspberry Pi 4 (ARM64, 2GB minimum, 4GB recommended) - SD card (16GB minimum, 32GB recommended) - Laptop for flashing the image - Serial console access (optional but useful for debugging)</p> <p>Download the latest Alpine Linux ARM64 image from <a href="https://www.alpinelinux.org/downloads/">https://www.alpinelinux.org/downloads/</a>. Using current images helps keep kernel, firmware, and boot settings aligned.</p> <p>Flash the image using <code>dd</code> or Balena Etcher:</p> <div class="sourceCode" id="cb1"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> dd if=alpine-latest-aarch64.iso of=/dev/sdX bs=4M status=progress</span> <span id="cb1-2"><a href="#cb1-2" aria-hidden="true" tabindex="-1"></a><span class="fu">sync</span></span></code></pre></div> <p>Replace <code>/dev/sdX</code> with your SD card device. Verify with <code>lsblk</code> first.</p> <h1 data-number="3" id="installation-workflow"><span class="header-section-number">3</span> Installation Workflow</h1> <h2 data-number="3.1" id="initial-setup"><span class="header-section-number">3.1</span> Initial Setup</h2> <p>Insert the SD card into the Pi and connect power. Alpine boots into a live environment. Log in as root (no password required).</p> <p>Run the interactive setup:</p> <div class="sourceCode" id="cb2"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">setup-alpine</span></span></code></pre></div> <p>This wizard configures hostname, timezone, network (DHCP for now), and package cache. For a headless system, accept defaults and skip password setup initially—you’ll secure the system after installation.</p> <h2 data-number="3.2" id="partitioning"><span class="header-section-number">3.2</span> Partitioning</h2> <p>Alpine’s default root filesystem is in RAM. To persist data, you must create a permanent root partition.</p> <p>Install partitioning tools:</p> <div class="sourceCode" id="cb3"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">apk</span> add e2fsprogs cfdisk</span></code></pre></div> <p>Launch the partitioner:</p> <div class="sourceCode" id="cb4"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">cfdisk</span> /dev/mmcblk0</span></code></pre></div> <p>Alpine uses MBR partitioning, supporting up to 4 primary partitions. The SD card arrives with partition 1 (boot, FAT16). Create partition 2 for the root filesystem:</p> <ul> <li>Partition 1: 256MB FAT16 (boot, already exists)</li> <li>Partition 2: Remainder ext4 (root)</li> </ul> <p>After partitioning, format the root partition:</p> <div class="sourceCode" id="cb5"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="ex">mkfs.ext4</span> /dev/mmcblk0p2</span></code></pre></div> <h2 data-number="3.3" id="boot-restructure"><span class="header-section-number">3.3</span> Boot Restructure</h2> <p>The key step many guides miss: Alpine’s boot must be explicitly configured for the Pi. The standard <code>setup-disk</code> command does not account for ARM bootloader requirements.</p> <p>Mount the new root filesystem:</p> <div class="sourceCode" id="cb6"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="fu">mount</span> /dev/mmcblk0p2 /mnt</span></code></pre></div> <p>Set a flag to force Alpine to use the FAT boot partition:</p> <div class="sourceCode" id="cb7"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="bu">export</span> <span class="va">FORCE_BOOTFS</span><span class="op">=</span>1</span></code></pre></div> <p>Now run the disk setup:</p> <div class="sourceCode" id="cb8"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="ex">setup-disk</span> <span class="at">-m</span> sys /mnt</span></code></pre></div> <p>This copies the Alpine root filesystem to <code>/mnt</code>, configures the bootloader, and sets up the kernel and initramfs with proper ARM naming conventions. The <code>-m sys</code> flag ensures the system runs in <q>sys</q> mode (persistent root), not <q>diskless</q> mode.</p> <h2 data-number="3.4" id="fstab-configuration"><span class="header-section-number">3.4</span> fstab Configuration</h2> <p>After installation, the system still needs to mount the boot partition explicitly on subsequent boots. Edit the fstab:</p> <div class="sourceCode" id="cb9"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" aria-hidden="true" tabindex="-1"></a><span class="fu">vi</span> /mnt/etc/fstab</span></code></pre></div> <p>Add an entry for the boot partition:</p> <pre class="fstab"><code>/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0</code></pre> <p>This ensures the FAT boot partition is accessible if your system needs to update the kernel or bootloader later. Some use cases (like kernel debugging) require direct access.</p> <h2 data-number="3.5" id="users-and-packages"><span class="header-section-number">3.5</span> Users and Packages</h2> <p>Chroot into the new system to complete configuration:</p> <div class="sourceCode" id="cb11"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" aria-hidden="true" tabindex="-1"></a><span class="fu">chroot</span> /mnt /bin/ash</span></code></pre></div> <p>Create a non-root user for day-to-day operations:</p> <div class="sourceCode" id="cb12"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" aria-hidden="true" tabindex="-1"></a><span class="ex">adduser</span> admin</span></code></pre></div> <p>Set a strong password when prompted.</p> <p>Install essential packages:</p> <div class="sourceCode" id="cb13"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" aria-hidden="true" tabindex="-1"></a><span class="ex">apk</span> add doas docker docker-compose git curl vim openssh</span></code></pre></div> <ul> <li><code>doas</code>: Lightweight sudo replacement</li> <li><code>docker</code>, <code>docker-compose</code>: Container runtime and orchestration</li> <li><code>git</code>, <code>curl</code>, <code>vim</code>: Development and debugging tools</li> <li><code>openssh</code>: Remote access</li> </ul> <p>Configure <code>doas</code> to allow the admin user to run privileged commands without a password:</p> <div class="sourceCode" id="cb14"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" aria-hidden="true" tabindex="-1"></a><span class="bu">echo</span> <span class="st">"permit persist :admin"</span> <span class="op">>></span> /etc/doas.d/doas.conf</span></code></pre></div> <p>Enable Docker to start at boot:</p> <div class="sourceCode" id="cb15"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" aria-hidden="true" tabindex="-1"></a><span class="ex">rc-update</span> add docker boot</span></code></pre></div> <p>Add the admin user to the docker group so they can run containers without <code>doas</code>:</p> <div class="sourceCode" id="cb16"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" aria-hidden="true" tabindex="-1"></a><span class="ex">addgroup</span> admin docker</span></code></pre></div> <p>Exit the chroot and unmount the filesystems:</p> <div class="sourceCode" id="cb17"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" aria-hidden="true" tabindex="-1"></a><span class="bu">exit</span></span> <span id="cb17-2"><a href="#cb17-2" aria-hidden="true" tabindex="-1"></a><span class="fu">umount</span> <span class="at">-R</span> /mnt</span></code></pre></div> <p>Now power down the Pi, remove the SD card, and insert it into the Raspberry Pi 4.</p> <h1 data-number="4" id="first-boot-and-verification"><span class="header-section-number">4</span> First Boot and Verification</h1> <p>When the Pi boots, it loads the kernel from the FAT partition and mounts the ext4 root filesystem. If everything is configured correctly, you’ll see Alpine’s boot messages and a login prompt.</p> <p>If the Pi fails to boot or displays a flashing green light without progress: - The boot partition is misconfigured - The kernel or initramfs is missing or misnamed - The fstab is preventing the root mount</p> <p>Serial console access helps diagnose these issues. If unavailable, re-insert the SD card into your laptop and verify that <code>/dev/mmcblk0p1</code> contains <code>kernel*.img</code> and <code>initramfs*.img</code> files. Recent Alpine versions use names like <code>vmlinuz-rpi4</code> and <code>initramfs-rpi4</code>; older versions used differently named files.</p> <p>Log in as the admin user you created:</p> <div class="sourceCode" id="cb18"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" aria-hidden="true" tabindex="-1"></a><span class="fu">ssh</span> admin@raspberry-pi-ip</span></code></pre></div> <p>Verify Docker is running:</p> <div class="sourceCode" id="cb19"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" aria-hidden="true" tabindex="-1"></a><span class="ex">docker</span> ps</span></code></pre></div> <p>If successful, you have a minimal, bootable Alpine Linux system.</p> <h1 data-number="5" id="networking-and-security"><span class="header-section-number">5</span> Networking and Security</h1> <h2 data-number="5.1" id="static-ip-configuration"><span class="header-section-number">5.1</span> Static IP Configuration</h2> <p>Alpine uses OpenRC for network management. Assign a static IP via your router’s DHCP reservation, or configure Alpine directly:</p> <div class="sourceCode" id="cb20"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" aria-hidden="true" tabindex="-1"></a><span class="fu">vi</span> /etc/network/interfaces</span></code></pre></div> <p>Replace the DHCP entry with:</p> <div class="sourceCode" id="cb21"><pre class="sourceCode ini"><code class="sourceCode ini"><span id="cb21-1"><a href="#cb21-1" aria-hidden="true" tabindex="-1"></a><span class="dt">auto eth0</span></span> <span id="cb21-2"><a href="#cb21-2" aria-hidden="true" tabindex="-1"></a><span class="dt">iface eth0 inet static</span></span> <span id="cb21-3"><a href="#cb21-3" aria-hidden="true" tabindex="-1"></a><span class="dt"> address 192.168.1.50</span></span> <span id="cb21-4"><a href="#cb21-4" aria-hidden="true" tabindex="-1"></a><span class="dt"> netmask 255.255.255.0</span></span> <span id="cb21-5"><a href="#cb21-5" aria-hidden="true" tabindex="-1"></a><span class="dt"> gateway 192.168.1.1</span></span> <span id="cb21-6"><a href="#cb21-6" aria-hidden="true" tabindex="-1"></a><span class="dt"> dns-nameserver 1.1.1.1</span></span></code></pre></div> <p>Restart networking:</p> <div class="sourceCode" id="cb22"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> rc-service networking restart</span></code></pre></div> <h2 data-number="5.2" id="firewall"><span class="header-section-number">5.2</span> Firewall</h2> <p>Alpine ships with netfilter but no firewall daemon. Install UFW for simple rule management:</p> <div class="sourceCode" id="cb23"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> apk add ufw</span> <span id="cb23-2"><a href="#cb23-2" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> rc-service ufw start</span> <span id="cb23-3"><a href="#cb23-3" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> rc-update add ufw boot</span></code></pre></div> <p>Allow only SSH (port 22) and HTTPS (port 443):</p> <div class="sourceCode" id="cb24"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> ufw default deny incoming</span> <span id="cb24-2"><a href="#cb24-2" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> ufw default allow outgoing</span> <span id="cb24-3"><a href="#cb24-3" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> ufw allow 22/tcp</span> <span id="cb24-4"><a href="#cb24-4" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> ufw allow 443/tcp</span> <span id="cb24-5"><a href="#cb24-5" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> ufw enable</span></code></pre></div> <p><strong>Critical note on IPv6:</strong> Alpine ARM builds do not reliably support IPv6. Disable it in UFW:</p> <div class="sourceCode" id="cb25"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> vi /etc/default/ufw</span></code></pre></div> <p>Set:</p> <div class="sourceCode" id="cb26"><pre class="sourceCode ini"><code class="sourceCode ini"><span id="cb26-1"><a href="#cb26-1" aria-hidden="true" tabindex="-1"></a><span class="dt">IPV6</span><span class="ot">=</span><span class="kw">no</span></span></code></pre></div> <p>This prevents IPv6 scanning and unexpected traffic. If you need IPv6 later, re-enable after testing thoroughly.</p> <h2 data-number="5.3" id="ssh-key-authentication"><span class="header-section-number">5.3</span> SSH Key Authentication</h2> <p>Remove password-based SSH authentication:</p> <div class="sourceCode" id="cb27"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> vi /etc/ssh/sshd_config</span></code></pre></div> <p>Set:</p> <pre class="conf"><code>PasswordAuthentication no PubkeyAuthentication yes</code></pre> <p>Copy your public key to the Pi:</p> <div class="sourceCode" id="cb29"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" aria-hidden="true" tabindex="-1"></a><span class="ex">ssh-copy-id</span> <span class="at">-i</span> ~/.ssh/id_rsa.pub admin@192.168.1.50</span></code></pre></div> <p>Restart SSH:</p> <div class="sourceCode" id="cb30"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> rc-service sshd restart</span></code></pre></div> <p>Now you can SSH into the Pi without a password, and password attacks are impossible.</p> <h1 data-number="6" id="system-updates"><span class="header-section-number">6</span> System Updates</h1> <p>Alpine updates are straightforward but require care on minimal systems. Update the package cache:</p> <div class="sourceCode" id="cb31"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> apk update</span></code></pre></div> <p>Upgrade packages:</p> <div class="sourceCode" id="cb32"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb32-1"><a href="#cb32-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> apk upgrade</span></code></pre></div> <p>Kernel updates are applied separately:</p> <div class="sourceCode" id="cb33"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb33-1"><a href="#cb33-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> apk add <span class="at">--upgrade</span> linux-rpi4</span></code></pre></div> <p>After a kernel update, reboot:</p> <div class="sourceCode" id="cb34"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb34-1"><a href="#cb34-1" aria-hidden="true" tabindex="-1"></a><span class="fu">sudo</span> reboot</span></code></pre></div> <p>Watch the Pi boot process. If it fails, the bootloader or initramfs configuration may need adjustment.</p> <h1 data-number="7" id="docker-and-container-management"><span class="header-section-number">7</span> Docker and Container Management</h1> <p>With Docker running and the system secured, you’re ready for containerized workloads. Alpine includes Docker and Docker Compose in its repositories. No need for external installation scripts.</p> <p>Verify Docker works:</p> <div class="sourceCode" id="cb35"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb35-1"><a href="#cb35-1" aria-hidden="true" tabindex="-1"></a><span class="ex">docker</span> run <span class="at">--rm</span> alpine echo <span class="st">"Hello from Alpine"</span></span></code></pre></div> <p>Pull and run a basic service. For example, a Caddy reverse proxy:</p> <div class="sourceCode" id="cb36"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb36-1"><a href="#cb36-1" aria-hidden="true" tabindex="-1"></a><span class="ex">docker</span> run <span class="at">-d</span> <span class="dt">\</span></span> <span id="cb36-2"><a href="#cb36-2" aria-hidden="true" tabindex="-1"></a> <span class="at">-p</span> 443:443 <span class="dt">\</span></span> <span id="cb36-3"><a href="#cb36-3" aria-hidden="true" tabindex="-1"></a> <span class="at">-v</span> /etc/caddy:/etc/caddy <span class="dt">\</span></span> <span id="cb36-4"><a href="#cb36-4" aria-hidden="true" tabindex="-1"></a> <span class="at">-v</span> /data/caddy:/data/caddy <span class="dt">\</span></span> <span id="cb36-5"><a href="#cb36-5" aria-hidden="true" tabindex="-1"></a> caddy:latest caddy run <span class="at">--config</span> /etc/caddy/Caddyfile</span></code></pre></div> <p>Docker containers on Alpine follow the same patterns as any Linux distribution. The advantage is that Alpine’s minimal host system leaves more resources for container workloads.</p> <h1 data-number="8" id="common-gotchas"><span class="header-section-number">8</span> Common Gotchas</h1> <p><strong>Boot partition permissions:</strong> If you later update the kernel and the boot partition is not mounted, new kernel files won’t be written to the FAT partition. Always ensure <code>/dev/mmcblk0p1</code> is mounted before kernel updates.</p> <p><strong>ARM64 image compatibility:</strong> Not all Docker images support ARM64. Before pulling an image, check its manifest on Docker Hub or Quay. If an image is x86-only, the pull succeeds but the container fails at runtime with <q>exec format error.</q></p> <p><strong>Memory and swap:</strong> Alpine on a 4GB Pi has ample memory for most workloads, but intensive operations (like building images locally) may benefit from swap. Create a swapfile if needed, but understand that swapping over SD card storage is slow.</p> <p><strong>OpenRC vs systemd:</strong> Alpine uses OpenRC instead of systemd. Service files are simple shell scripts in <code>/etc/init.d/</code>. If you’re used to systemd, expect a different operational model, but also expect lower overhead and faster boots.</p> <h1 data-number="9" id="next-steps"><span class="header-section-number">9</span> Next Steps</h1> <p>Your Alpine Pi now has a minimal, secure foundation. From here:</p> <ul> <li>Deploy containerized services using Docker Compose</li> <li>Set up a reverse proxy (Caddy or Traefik) for TLS termination</li> <li>Configure container management tools (Portainer, Rancher) for visibility</li> <li>Implement dynamic DNS automation to maintain public accessibility</li> <li>Add monitoring with Prometheus and Grafana</li> </ul> <p>Alpine’s efficiency makes it ideal for long-running, low-power home infrastructure. The discipline of working with minimal systems teaches valuable lessons about what’s truly essential.</p> <h1 data-number="10" id="verification-checklist"><span class="header-section-number">10</span> Verification Checklist</h1> <p>Before declaring the installation complete:</p> <ul class="task-list"> <li><label><input type="checkbox"></input>Alpine boots and logs in without password as admin user</label></li> <li><label><input type="checkbox"></input>SSH key authentication works; password authentication is disabled</label></li> <li><label><input type="checkbox"></input>Docker runs and can pull/run containers</label></li> <li><label><input type="checkbox"></input>Static IP is assigned and stable</label></li> <li><label><input type="checkbox"></input>Firewall allows only ports 22 and 443 inbound</label></li> <li><label><input type="checkbox"></input>IPv6 is disabled</label></li> <li><label><input type="checkbox"></input>fstab includes boot partition mount</label></li> <li><label><input type="checkbox"></input><code>doas</code> is configured for passwordless privilege escalation</label></li> <li><label><input type="checkbox"></input>System clock is correct</label></li> <li><label><input type="checkbox"></input>Kernel and initramfs files exist in <code>/media/mmcblk0p1</code></label></li> </ul> <p>With this checklist passed, you have a production-ready Alpine Linux foundation for containerized workloads.</p>

Previous Arch Linux Installa… Next Boot From SD Live o…

Comments

No comments yet
Be the first to comment!