If you have any special requests, please send an email. Only architectures supported by each Linux distribution upstream are listed, and named after the upstream port (e.g. Debian uses "amd64" while Alpine uses "x86_64").

Note: support for multi-arch builds is underway, but not yet available.

The "native" column is checked if these builds run on native hardware for that architecture, if unchecked the builds are run on emulated hardware and may suffer from poor performance.

Support lifecycle

The support lifecycle for each build image follows the upstream support cycle. Each supported upstream release is generally offered on sr.ht, as well as the bleeding edge or development releases if applicable. No sooner than two weeks after a release becomes unsupported upstream, it will be unsupported on builds.sr.ht — and anyone who's submitted recent builds using those images will get an email warning them of the impending breakage.

It's recommended that you use aliases like "alpine/latest" or "debian/testing" rather than using a specific release in your build manifests.

#Alpine Linux

Maintainer: Drew DeVault sir@cmpwn.com

Support policy: upstream

packages

The packages array is installed with apk add.

repositories

To add custom apk repositories, use repo-url key-url key-name (separated with spaces), where repo-url is the URL of the package repository and key-url is a URL from where the signing key may be downloaded, and key-name is the name of the file written to /etc/apk/keys/. If the name of the repo is prefixed with an @, it will use that prefix in apk.

Example:

repositories:
  sr.ht: >
    https://mirror.sr.ht/alpine/sr.ht/
    https://mirror.sr.ht/alpine/sr.ht/alpine%40sr.ht.rsa.pub
    alpine@sr.ht.rsa.pub

#Arch Linux

Maintainer: Drew DeVault sir@cmpwn.com

packages

The package array is installed with yay -Syu (AUR packages are transparently installed).

repositories

To add custom pacman repositories, use url#key-id, where url is the URL of the package repository and key-id is the ID of the published PGP key the packages are signed with.

#Debian

Maintainer: Taavi Väänänen taavi@debian.org

Support policy: stable, testing, unstable, and oldstable are supported. See also: upstream releases

packages

The packages array is installed with apt-get install.

repositories

To add custom repositories, specify url release component key-id (separated by spaces), where url is the URL of the package repository, release is e.g. bullseye or bookworm, component is e.g. main, contrib, non-free or non-free-firmware (since bookworm), and key-id is an optional PGP key ID to add to the system keyring. Example:

repositories:
  sr.ht: https://mirror.sr.ht/debian/sr.ht/ bookworm main DEADBEEFCAFEF00D

#Fedora Linux

Maintainer: Haowen Liu lhw@lunacd.com

packages

The packages array is installed with dnf install.

repositories

Given the following list of repositories in your manifest:

repositories:
  example: https://example.org

The following commands will be used to configure it:

Fedora 41 and later:

dnf config-manager addrepo --from-repofile=https://example.org
dnf config-manager setopt example.enabled=1

Fedora 40 and earlier:

dnf config-manager --add-repo https://example.org
dnf config-manager --set-enabled example

#FreeBSD

Maintainer: none

Support policy: Upstream production releases are supported.

packages

The packages array is installed with pkg install.

repositories

Custom package repositories are not supported on FreeBSD builds.

#Guix System

Maintainer: Unwox me@unwox.com

Guix System support for builds.sr.ht is actively being maintained here. There is a cookbook to get started.

packages

The packages are installed with guix install.

repositories

Specifying additional channels via build manifest is not supported.

#NetBSD

Maintainer: Michael Forney mforney@mforney.org

Support policy: the most recent release and the version prior are supported. See also: upstream release cycle

packages

The packages array is installed with pkgin.

repositories

Custom package repositories are not supported on NetBSD builds.

#NixOS

Maintainer: Francesco Gazzetta fgaz@fgaz.me

Support policy: NixOS upstream does not have a clear support policy, but usually old releases continue to get security fixes for a short amount of time after they are superseded. We ship the latest stable version (channel nixos-YY.MM) and the latest bleeding edge (channel nixos-unstable). We remove old versions after they are marked as "End of life" at status.nixos.org.

packages

The packages array is installed with nix-env -iA. Since it's possible to specify multiple channels, you must provide the full selection path, for example nixos.hello.

repositories

To add custom channels, use channel-name: channel-url. The channel name is relevant, since channel-name: channel-url will execute the commands nix-channel --add channel-url channel-name and nix-channel --update channel-name.

Example:

repositories:
  nixpkgs: https://nixos.org/channels/nixpkgs-unstable

By default, no user channels are present. However, like in a fresh NixOS installation, there is a root channel named nixos set to

• https://nixos.org/channels/nixos-XX.YY in nixos/latest and nixos/XX.YY
• https://nixos.org/channels/nixos-unstable in nixos/unstable

which is the channel the image was built from.

flakes

Like in a standard Nix(OS) installation, flakes are not enabled by default. A good way to use flakes without having to pass --extra-experimental-features to every nix invocation is to use the NIX_CONFIG environment variable instead:

environment:
  NIX_CONFIG: "experimental-features = nix-command flakes"

#OpenBSD

Maintainer: Jarkko Oranen oranenj@iki.fi

Support policy: the most recent release and the version prior are supported. See also: upstream release cycle

notes

Binary patches are applied to the base system using syspatch.

packages

The packages array is installed with pkg_add.

repositories

Custom package repositories are not supported on OpenBSD builds.

#Rocky Linux

Maintainer: Haowen Liu lhw@lunacd.com

packages

The packages array is installed with dnf install.

repositories

Given the following list of repositories in your manifest:

repositories:
  example: https://example.org

The following commands will be used to configure it:

dnf config-manager --add-repo https://example.org
dnf config-manager --set-enabled example

#Ubuntu

Maintainer: Haowen Liu lhw@lunacd.com

Support cycle: all releases under standard support. See the upstream support schedule for more information.

packages

The packages array is installed with apt-get install.

repositories

To add custom repositories, specify url release component key-id (separated by spaces), where url is the URL of the package repository, release is e.g. bionic or cosmic, component is e.g. main, contrib or non-free, and key-id is an optional PGP key ID to add to the system keyring. Example:

repositories:
  sr.ht: https://mirror.sr.ht/debian/sr.ht/ cosmic main DEADBEEFCAFEF00D