Debian 13 "Trixie" review: the stability baseline that self-hosted software expects

What changed from Bookworm

Debian 13 was officially released on August 9, 2025, following a two-year development cycle that introduced 14,100 new packages and updated 44,326 existing ones. The distribution now ships nearly 70,000 packages totaling 403 GB of disk usage across 1.4 billion lines of code. The jump from Linux kernel 6.1 LTS in Bookworm to 6.12 LTS in Trixie brings improved support for Intel Arrow Lake and Lunar Lake processors, AMD RDNA 4 graphics, Raspberry Pi 5 compatibility, and real-time PREEMPT_RT support.

The transition to 64-bit time values across all architectures except legacy i386 addresses the Year 2038 problem by allowing systems to represent dates beyond January 19, 2038. APT 3.0 replaces version 2.x with smarter dependency resolution, color-coded output for clearer status messages, and Zstandard compression support that accelerates package list decompression by up to three times. The temporary file directories /tmp and /var/tmp now default to tmpfs on fresh installations, storing temporary files in RAM instead of on disk to reduce write cycles and improve performance for workloads with heavy temporary file usage.

Security hardening arrives through hardware-level exploit mitigation on amd64 and arm64 systems. Intel Control-flow Enforcement Technology and ARM Pointer Authentication with Branch Target Identification help defend against Return-Oriented Programming and Call/Jump-Oriented Programming attacks when running on compatible processors. The entire software archive now builds with position-independent executables enabled by default, strengthening the security posture of every service without requiring configuration changes.

Why homelabbers still default to it

Debian remains the silent assumption behind most self-hosted software documentation. Docker Compose examples, reverse proxy tutorials, and database setup guides rarely specify a distribution by name, but the package versions and filesystem layouts they reference typically match Debian stable. This alignment means fewer surprises when following upstream instructions and less time spent translating documentation written for other distributions.

The five-year support lifecycle allows infrastructure to outlive the churn of container orchestration trends and framework rewrites. Debian 13 receives full security updates until August 2028, followed by Long Term Support through June 2030. For operators managing services that need to survive across apartment moves, hardware refreshes, or team transitions, this predictability reduces the maintenance burden. The upgrade path from Bookworm to Trixie, while manual, follows the same process Debian has refined over decades.

The distribution prioritizes reproducible builds and documented behavior over feature velocity. Nearly all packages can now be verified to produce byte-for-byte identical results when rebuilt, a property that matters when auditing supply chains or validating container base images. The conservative package selection means system libraries remain stable across point releases, preventing the breakage that occurs when dependencies shift underneath long-running services.

Installation and upgrade considerations

Fresh installations offer the familiar Debian Installer with several enhancements. HTTP Boot support allows booting installation media directly from web servers on compatible UEFI and U-Boot firmware, eliminating the need for physical USB drives or optical media. The installer now includes Btrfs rescue functionality for systems originally configured via the Calamares installer, and the default partitioning unit has changed from megabytes to gigabytes to reduce input errors on modern large drives. Speech synthesis support has improved for accessibility, and the installer disables CD-ROM sources when the installation medium is a USB stick or SD card.

Upgrading from Debian 12 Bookworm requires editing /etc/apt/sources.list to replace all instances of bookworm with trixie, including bookworm-security and bookworm-updates. The official release notes recommend removing bookworm-backports entries before the upgrade and adding trixie-backports afterward if needed. The upgrade process typically involves running apt update, apt upgrade without new packages, then apt full-upgrade to install all new packages and dependencies. During the upgrade, some packages will be removed as obsolete, and services like RabbitMQ require special migration steps documented in the release notes.

Several breaking changes demand attention. OpenSSH no longer supports DSA keys, the /tmp directory now uses tmpfs by default, and /etc/sysctl.conf is no longer honored by systemd. MariaDB major version upgrades only work reliably after a clean shutdown, and the OpenLDAP client libldap2 now uses OpenSSL instead of GnuTLS for TLS support. Users running i386 systems should not upgrade to Trixie, as there is no official kernel or installer for 32-bit hardware; Debian recommends reinstalling as amd64 where possible or retiring the hardware.

Desktop environments and server tools

Desktop users gain GNOME 48 with digital wellbeing features including screen-time limits and grayscale modes, and KDE Plasma 6.3 based on Qt 6 and KDE Frameworks 6. The transition to Plasma 6 brings a complete rewrite of the desktop environment, though some upgrade quirks exist and are tracked on the Debian wiki. LXQt 2.1 introduces comprehensive Wayland support through dedicated backends, while Xfce, MATE, Cinnamon, and LXDE continue to receive incremental updates. Wayland becomes the default display server for GNOME and KDE, with X11 remaining available for compatibility.

Server administrators benefit from updated language runtimes including Python 3.13, PHP 8.3, OpenJDK 21, and GCC 14.2. PostgreSQL 17, MariaDB 11.4, and OpenSSL 3.3 provide current database and cryptographic capabilities. The curl package now ships wcurl as a wget alternative and includes HTTP/3 support via the --http3 flag. Cloud images for AWS, Azure, Google Cloud, and generic virtualized environments include cloud-init automation hooks and optimized kernel packages for fast instance startup.

Container and virtualization tooling remains a primary use case. Debian 13 serves as the upstream base for official Docker and Podman images, with both standard and slim variants available on Docker Hub. The distribution provides a stable foundation for running LXC, systemd-nspawn, or KVM workloads, with the kernel 6.12 improvements to I/O scheduling benefiting NVMe-backed storage particularly in high-density virtualization environments.

Architecture support and hardware compatibility

Debian 13 officially supports seven architectures at initial release: amd64, arm64, armel (upgrades only), armhf, mips64el, ppc64el, and the newly added riscv64. The inclusion of RISC-V 64-bit support marks a significant milestone for the open hardware ecosystem, allowing users to run a full Debian environment on RISC-V processors with access to the complete package repository. The i386 architecture no longer has an official installer or kernel, with remaining packages intended solely as a compatibility layer for running 32-bit software on 64-bit amd64 systems that support the SSE2 instruction set.

Hardware support improvements come primarily through kernel 6.12 LTS, which introduces drivers for Apple ARM-based MacBook MTP and SPI keyboards, expanded support for Intel and AMD graphics including RDNA 4, and improved compatibility with modern Wi-Fi chipsets. The kernel receives official support with bug and security updates until December 2026, providing a stable foundation for the distribution lifecycle. Secure Boot functionality improves through the shim-signed package on AMD64 and ARM64 systems.

The armel architecture sees its final release with Trixie, and MIPS architectures including mipsel have been completely removed. Users on affected hardware should plan migration to supported architectures or consider remaining on Debian 12 Bookworm, which continues to receive security updates until 2028. The reduction in supported architectures reflects Debian's shift toward focusing resources on platforms with active upstream development and user demand.