Installing Amiberry on Linux via Package Repository
Amiberry provides a self-hosted APT/YUM package repository at packages.amiberry.com,
allowing you to install and receive automatic updates through your system’s package manager.
Alternatives: Amiberry is also available on Flathub, which works on all major Linux distributions without any additional configuration, and as a no-install AppImage for x86_64 and aarch64 from every GitHub release.
Quick Install (One-Liner)
curl -fsSL https://packages.amiberry.com/install.sh | sudo sh
This script auto-detects your distribution and configures the repository.
After setup, install with sudo apt install amiberry (Debian/Ubuntu) or sudo dnf install amiberry (Fedora).
Manual Installation — Ubuntu / Debian
Modern format (Ubuntu 24.04+, Debian 13+)
# Download GPG key
curl -fsSL https://packages.amiberry.com/gpg.key \
| sudo tee /usr/share/keyrings/amiberry-archive-keyring.gpg > /dev/null
# Add repository (DEB822 format)
echo "Types: deb
URIs: https://packages.amiberry.com/apt
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Architectures: $(dpkg --print-architecture)
Signed-By: /usr/share/keyrings/amiberry-archive-keyring.gpg" \
| sudo tee /etc/apt/sources.list.d/amiberry.sources
# Install
sudo apt update && sudo apt install amiberry
Legacy format (Ubuntu 22.04, Debian 12, or if DEB822 format is not supported)
# Download GPG key
curl -fsSL https://packages.amiberry.com/gpg.key \
| sudo tee /usr/share/keyrings/amiberry-archive-keyring.gpg > /dev/null
# Add repository (legacy one-line format)
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/amiberry-archive-keyring.gpg] \
https://packages.amiberry.com/apt $(. /etc/os-release && echo $VERSION_CODENAME) main" \
| sudo tee /etc/apt/sources.list.d/amiberry.list
# Install
sudo apt update && sudo apt install amiberry
Update Amiberry (APT)
sudo apt update && sudo apt upgrade amiberry
Manual Installation — Fedora
# Add repository
sudo curl -fsSL https://packages.amiberry.com/rpm/amiberry.repo \
-o /etc/yum.repos.d/amiberry.repo
# Import GPG key
sudo rpm --import https://packages.amiberry.com/gpg.asc
# Install
sudo dnf install amiberry
Update Amiberry (DNF)
sudo dnf update amiberry
AppImage
Each GitHub release publishes Amiberry-<version>-x86_64.AppImage for Intel and AMD systems and Amiberry-<version>-aarch64.AppImage for 64-bit ARM systems, with a corresponding .zsync file for each image. Download the matching image from the GitHub releases page, make it executable, and run it:
chmod +x Amiberry-<version>-x86_64.AppImage
./Amiberry-<version>-x86_64.AppImage
Replace x86_64 with aarch64 on 64-bit ARM. AppImage is a single-file, no-install option and lets stable and preview releases run side by side. Native packages remain the best choice for system integration and distribution-managed updates; Flatpak is the broad fallback and sandboxed option.
AppImage mount mode needs working FUSE. The image has a static runtime and does not require the legacy libfuse2 package; do not install it just for Amiberry. If FUSE is unavailable, run without mounting:
./Amiberry-<version>-x86_64.AppImage --appimage-extract-and-run
AppImages require glibc 2.35 or newer. On an older distribution, use Flatpak or a supported native package rather than replacing the system glibc.
Portable home and updates
To keep configuration and writable data beside a specific image, create a sibling directory named for the complete image filename before its first launch:
mkdir Amiberry-8.4.2-x86_64.AppImage.home
./Amiberry-8.4.2-x86_64.AppImage
AppImage managers can integrate the image and use its .zsync file for updates. The Amiberry Linux updater only notifies about updates; it does not update an AppImage itself.
AppImage troubleshooting
If normal launch reports a FUSE or mount error, use --appimage-extract-and-run as shown above. If it reports an unsupported GLIBC version, use Flatpak or a supported native package; never replace the system glibc.
If it reports a missing libOpenGL.so.0, libwayland-client.so.0, libasound.so.2 or libdbus-1.so.3, install your distribution’s OpenGL (libglvnd), Wayland client, ALSA and D-Bus runtime packages. The AppImage deliberately uses these from the host so it works with your graphics drivers and sound server.
The AppImage uses your system’s certificate store for update checks and downloads. If your trust store lives somewhere non-standard, point SSL_CERT_FILE (or CURL_CA_BUNDLE) at the CA bundle before launching the image.
Supported Distributions
| Distribution | Version | Repository suite | Architectures |
|---|---|---|---|
| Ubuntu | 22.04 LTS (Jammy) | jammy | amd64 |
| Ubuntu | 24.04 LTS (Noble) | noble | amd64 |
| Ubuntu | 25.10 (Questing) | questing | amd64, arm64 |
| Ubuntu | 26.04 LTS (Resolute) | resolute | amd64, arm64 |
| Ubuntu | 26.10 (Stonking) | stonking | amd64, arm64 |
| Debian | 12 (Bookworm) | bookworm | amd64, arm64 |
| Debian | 13 (Trixie) | trixie | amd64, arm64 |
| Raspberry Pi OS | Bookworm, Trixie | bookworm, trixie | arm64 |
| Fedora | 44 | rpm | x86_64, aarch64 |
The install script also maps compatible derivatives to the matching base suite:
| Distribution | Version | Repository suite |
|---|---|---|
| Linux Mint | 21.x | jammy |
| Linux Mint | 22.x | noble |
| LMDE | 6 | bookworm |
| LMDE | 7 | trixie |
| Elementary OS | 7 | jammy |
| Elementary OS | 8 | noble |
| Pop!_OS | 22.04 | jammy |
| Pop!_OS | 24.04 | noble |
| Zorin OS | 17 | jammy |
| Zorin OS | 18 | noble |
| Devuan | 5 | bookworm |
| Devuan | 6 | trixie |
| Parrot OS | 6 | bookworm |
| Parrot OS | 7 | trixie |
| SparkyLinux | 7 | bookworm |
| SparkyLinux | 8 | trixie |
For manual APT setup on derivatives, use the repository suite shown above instead of the derivative distribution codename.
GPG Key Information
The repository is signed with the following key:
| Property | Value |
|---|---|
| Fingerprint | D74D52525340C442A4F8B657A12B57C04E1FE282 |
| Identity | Amiberry Package Signing packages@amiberry.com |
| Algorithm | RSA 4096 |
| Key URL | https://packages.amiberry.com/gpg.key |
To verify the key:
curl -fsSL https://packages.amiberry.com/gpg.key | gpg --show-keys
Troubleshooting
“GPG error: NO_PUBKEY …”
The GPG key is missing or outdated. Re-run the key import step:
curl -fsSL https://packages.amiberry.com/gpg.key \
| sudo tee /usr/share/keyrings/amiberry-archive-keyring.gpg > /dev/null
“Release file for … is not valid yet / has expired”
This can happen if Amiberry has not published a release in a while. Temporary workaround:
sudo apt update --allow-releaseinfo-change
If this recurs frequently, open an issue.
“Package ‘amiberry’ has no installation candidate”
Possible causes:
- Your distribution version is not in the supported list above
- Your architecture is not supported for your distro version (e.g.,
arm64on Ubuntu 22.04) - The repository was not configured correctly — re-run the install steps
“The Amiberry repository has no packages for …”
The install script found your release, but the repository does not publish a suite for it yet (new Ubuntu releases are added after their first Amiberry build). The script stops without changing your apt configuration. To try the packages of the closest older release, name its suite explicitly:
curl -fsSL https://packages.amiberry.com/install.sh | sudo AMIBERRY_APT_SUITE=resolute sh
Older-release packages can fail to install if your release has moved to newer library versions; Flatpak is the fallback in that case.
Conflicting versions (Flatpak + APT/DNF both installed)
If you have both the Flatpak and native package installed, the native APT/DNF version takes precedence in the application launcher. To use only one:
# Remove Flatpak version (keep native)
flatpak uninstall com.blitterstudio.amiberry
# OR remove native package (keep Flatpak)
sudo apt remove amiberry # or: sudo dnf remove amiberry