---
title: builds.sr.ht compatibility matrix
---
If you have any special requests, please [send an
email](mailto:~sircmpwn/sr.ht-discuss@lists.sr.ht). 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
Support policy: [upstream](https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases)
Alpine Edge |
image: alpine/edge
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhf | | | |
arch: ppc64el | | | |
arch: s390x | | | |
arch: x86_64 (default) |
✓ |
✓ |
daily |
arch: x86 | | | |
Alpine 3.13 |
image: alpine/latest or
image: alpine/3.13
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhf | | | |
arch: ppc64el | | | |
arch: s390x | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
arch: x86 | | | |
Alpine 3.12 |
image: alpine/old or
image: alpine/3.12
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhf | | | |
arch: ppc64el | | | |
arch: s390x | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
arch: x86 | | | |
Alpine 3.11 |
image: alpine/3.11 or
image: alpine/older
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhf | | | |
arch: ppc64el | | | |
arch: s390x | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
arch: x86 | | | |
Alpine 3.10 |
image: alpine/3.10 or
image: alpine/oldest
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhf | | | |
arch: ppc64el | | | |
arch: s390x | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
arch: x86 | | | |
**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:
```yaml
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
Arch Linux |
image: archlinux
|
arch |
supported |
native |
updated |
arch: x86_64 (default) |
✓ |
✓ |
daily |
**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: Drew DeVault
Support policy: stable, testing, unstable, and oldstable are supported.
See also: [upstream releases](https://www.debian.org/releases/)
Debian Buster (stable) |
image: debian/stable or
image: debian/buster
|
arch |
supported |
native |
updated |
arch: arm64 | | | |
arch: amd64 (default) |
✓ |
✓ |
weekly |
arch: armel | | | |
arch: armhl | | | |
arch: i386 | | | |
arch: mips | | | |
arch: mips64el | | | |
arch: mipsel | | | |
arch: ppc64el | | | |
arch: s390x | | | |
Debian bullseye (testing) |
image: debian/testing or
image: debian/bullseye
|
arch |
supported |
native |
updated |
arch: arm64 | | | |
arch: amd64 (default) |
✓ |
✓ |
daily |
arch: armel | | | |
arch: armhl | | | |
arch: i386 | | | |
arch: mips | | | |
arch: mips64el | | | |
arch: mipsel | | | |
arch: ppc64el | | | |
arch: s390x | | | |
Debian Sid (unstable) |
image: debian/unstable or
image: debian/sid
|
arch |
supported |
native |
updated |
arch: arm64 (experimental) |
✓ |
✗ |
manually |
arch: amd64 (default) |
✓ |
✓ |
daily |
arch: armel | | | |
arch: armhl | | | |
arch: i386 | | | |
arch: mips | | | |
arch: mips64el | | | |
arch: mipsel | | | |
arch: ppc64el | | | |
arch: s390x | | | |
Debian Stretch (oldstable) |
image: debian/oldstable or
image: debian/stretch
|
arch |
supported |
native |
updated |
arch: arm64 | | | |
arch: amd64 (default) |
✓ |
✓ |
manually |
arch: armel | | | |
arch: armhl | | | |
arch: i386 | | | |
arch: mips | | | |
arch: mips64el | | | |
arch: mipsel | | | |
arch: ppc64el | | | |
arch: s390x | | | |
**packages**
The packages array is installed with `apt-get install`.
**repositories**
To add custom repositories, specify `url distro component key-id` (separated by
spaces), where `url` is the URL of the package repository, `distro` is e.g.
`jessie` or `stretch`, `component` is e.g. `main` or `non-free`, and `key-id` is
an optional PGP key ID to add to `apt-key`. Example:
```yaml
repositories:
sr.ht: https://mirror.sr.ht/debian/sr.ht/ stretch main DEADBEEFCAFEF00D
```
## Fedora
Maintainer: Timothée Floure
Fedora Rawhide |
image: fedora/rawhide or
image: fedora/34
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhfp | | | |
arch: x86_64 (default) |
✓ |
✓ |
daily |
Fedora 33 |
image: fedora/latest or
image: fedora/33
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhfp | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
Fedora 32 |
image: fedora/32
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armhfp | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
**packages**
The packages array is installed with `dnf install`.
**repositories**
Given the following list of repositories in your manifest:
```yaml
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
## FreeBSD
Maintainer: Simon Ser
Support policy: [Upstream production
releases](https://www.freebsd.org/releases/) are supported.
FreeBSD 13.x |
image: freebsd/latest or
image: freebsd/13.x
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: amd64 (default) |
✓ |
✓ |
weekly |
arch: i386 | | | |
arch: powerpc | | | |
arch: powerpc64 | | | |
arch: sparc64 | | | |
FreeBSD 12.x |
image: freebsd/12.x
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: amd64 (default) |
✓ |
✓ |
weekly |
arch: i386 | | | |
arch: powerpc | | | |
arch: powerpc64 | | | |
arch: sparc64 | | | |
FreeBSD 11.x |
image: freebsd/11.x
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: amd64 (default) |
✓ |
✓ |
weekly |
arch: i386 | | | |
arch: powerpc | | | |
arch: powerpc64 | | | |
arch: sparc64 | | | |
**packages**
The packages array is installed with `pkg install`.
A snapshot of the ports collection is available at `/usr/ports`. Git can be
used to update it to the latest commit.
**repositories**
Custom package repositories are not supported on FreeBSD builds.
## NixOS
Maintainer: Francesco Gazzetta
Support policy: NixOS upstream does not have a clear support policy. We ship the
latest stable version and the latest bleeding edge.
NixOS 20.09 |
image: nixos/latest or
image: nixos/20.09
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armv6 | | | |
arch: armv7 | | | |
arch: x86_64 (default) |
✓ |
✓ |
weekly |
NixOS unstable |
image: nixos/unstable
|
arch |
supported |
native |
updated |
arch: aarch64 | | | |
arch: armv6 | | | |
arch: armv7 | | | |
arch: x86_64 (default) |
✓ |
✓ |
daily |
**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:
```yaml
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.
## OpenBSD
Maintainer: Jarkko Oranen
Support policy: the most recent release and the version prior are supported. See
also: [upstream release cycle](https://www.openbsd.org/faq/faq5.html)
OpenBSD 6.8 |
image: openbsd/latest or
image: openbsd/6.8
|
arch |
supported |
native |
updated |
arch: alpha | | | |
arch: amd64 (default) |
✓ |
✓ |
as required |
arch: arm64 | | | |
arch: armv7 | | | |
arch: hppa | | | |
arch: i386 | | | |
arch: landisk | | | |
arch: loongson | | | |
arch: luna88k | | | |
arch: macppc | | | |
arch: octeon | | | |
arch: power64 | | | |
arch: sparc64 | | | |
OpenBSD 6.7 |
image: openbsd/6.7
|
arch |
supported |
native |
updated |
arch: alpha | | | |
arch: amd64 (default) |
✓ |
✓ |
as required |
arch: arm64 | | | |
arch: armv7 | | | |
arch: hppa | | | |
arch: i386 | | | |
arch: landisk | | | |
arch: loongson | | | |
arch: luna88k | | | |
arch: macppc | | | |
arch: octeon | | | |
arch: sgi | | | |
arch: sparc64 | | | |
**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.
## Ubuntu
Maintainer: New maintainer wanted; [email sr.ht-discuss](https://lists.sr.ht/~sircmpwn/sr.ht-discuss) to express interest
Support cycle: the latest LTS, previous LTS, and the next normal release of
Ubuntu are all supported. See the [upstream support schedule](https://wiki.ubuntu.com/Releases)
for more information.
Ubuntu Focal (20.04) |
image: ubuntu/lts or
image: ubuntu/focal or
image: ubuntu/20.04
|
arch |
supported |
native |
updated |
arch: arm64 | | | |
arch: amd64 (default) |
✓ |
✓ |
weekly |
arch: i386 | | | |
arch: ppc64el | | | |
arch: s390x | | | |
Ubuntu Groovy (20.10) |
image: ubuntu/next or
image: ubuntu/groovy or
image: ubuntu/20.10
|
arch |
supported |
native |
updated |
arch: arm64 | | | |
arch: amd64 (default) |
✓ |
✓ |
daily |
arch: i386 | | | |
arch: ppc64el | | | |
arch: s390x | | | |
Ubuntu Bionic (18.04) |
image: ubuntu/oldlts or
image: ubuntu/bionic or
image: ubuntu/18.04
|
arch |
supported |
native |
updated |
arch: arm64 | | | |
arch: amd64 (default) |
✓ |
✓ |
monthly |
arch: i386 | | | |
arch: ppc64el | | | |
arch: s390x | | | |
**packages**
The packages array is installed with `apt-get install`.
**repositories**
To add custom repositories, specify `url distro component key-id` (separated by
spaces), where `url` is the URL of the package repository, `distro` is e.g.
`bionic` or `cosmic`, `component` is e.g. `main` or `non-free`, and `key-id` is
an optional PGP key ID to add to `apt-key`. Example:
```yaml
repositories:
sr.ht: https://mirror.sr.ht/debian/sr.ht/ cosmic main DEADBEEFCAFEF00D
```
## 9front
Maintainer: Drew DeVault
Support cycle: no support guarantees are made for 9front
9front "NO THINKPAD" |
image: 9front
|
arch |
supported |
native |
updated |
arch: pc64 (default) |
✓ |
✓ |
manually |
**Caveats**
- Git submodules are not supported by git9
- 9front ships a dated Mercurial version which is not compatible with hg.sr.ht's
wire protocol
- Custom packages and custom repositories are not supported
- Shell access is not supported