Choose the image that matches your architecture and use case.
Alpine Linux is an independent, security-oriented and lightweight distribution built around musl libc, BusyBox and the apk package manager. Alpine 3.24.1 is the current stable release and provides standard, extended, virtualisation, cloud and embedded-oriented images.
Alpine Linux is primarily suited to servers, virtual machines and self-hosted services; authorized security testing, forensics and technical training; older computers, modest hardware and lightweight virtual machines. Before choosing it, compare the current release lifecycle with the length of support required for the machine. This distribution is based on independent, which influences package formats, repositories and much of the available documentation. The best choice depends on hardware support, preferred software, update policy and the amount of system administration the user wants to perform.
Read the release notes and installation guide before downloading. Select an image that matches the processor architecture and intended use: desktop, server, live media, virtual machine or another published edition. Test Wi-Fi, graphics, audio, storage and suspend from live media when that option is available. Back up important files before repartitioning, encryption changes or dual-boot installation. Security distributions should only be used against systems and networks you own or are explicitly authorized to assess. For production deployment, verify application compatibility, upgrade paths, backup restoration and the project security-support policy in a non-production environment first. Download from an official project page or mirror, compare the published SHA-256 checksum, and verify a signed checksum when the project provides one. After installation, apply updates before adding third-party repositories or drivers.
Memory and storage depend strongly on enabled services, workload, redundancy and retention. Size production systems from the official deployment documentation.
The download button first records an anonymous aggregated download counter and then redirects to the official source.
Six post-installation checks based on project documentation. Commands are examples for your own system, not an automatic installation script. Review your edition and current release notices first.
Follow the post-install recommendations to configure an ordinary account and administrative access. Do not perform everyday browsing as root.
Read project documentation: Use a normal login accountInspect /etc/apk/repositories. Use the installed stable branch; do not combine stable repositories with edge or testing to obtain a single newer package.
Read project documentation: Keep repositories on one release branchAfter backing up important configuration, run these commands in an authorized root shell. This updates the configured branch; it is not an instruction to change release branches.
Before you continue: Review errors before proceeding. Save work and plan any necessary service restart or reboot.
apk update && apk upgradeRead project documentation: Update installed packagesAfter upgrades, inspect .apk-new files. The update-conf utility can compare configuration changes; preserve local settings deliberately rather than accepting every replacement.
Before you continue: Incorrect configuration merges can interrupt networking or services.
Read project documentation: Review configuration differencesFor a workstation, follow the setup-desktop documentation to select a supported desktop. A headless server does not need this extra software.
Before you continue: Desktop installation changes the package and service set.
Read project documentation: Add a desktop only if requiredUse apk search to find packages and apk info to inspect them. Prefer repository packages that match the configured branch.
Read project documentation: Search before adding software