Latest release: 2.62 github releases. See snapd roadmap for details.

Repology overview

We use a third-party tool called Repology to track snapd version numbers across various Linux distributions.

On some distributions, a non-snap package will install the snapd snap which will subsequently update itself. This process is called re-execution. On such systems, Repology can only detect the version number of the native non-snap package and not the updated snapd from the snap.

Distributions that have reached their end-of-life are excluded from the list.

Ubuntu

Due to distribution policy snapd is not regularly updated to the latest available version. Snapd re-execution is supported on Ubuntu. The versions listed above are usually only relevant before the installation of the first snap. Outside of unusual circumstances, the Ubuntu package is synchronized from Debian. This process stops once an upcoming Ubuntu release is entering feature freeze.

Debian

Due to distribution policy snapd is not regularly updated to the latest available version. Snapd re-execution is supported on Debian. The versions listed above are usually only relevant before the installation of the first snap.

Resources for developers:

• Salsa (Debian gitlab repository)
• Tracker (package status)
• Continuous integration
• 2.61.1 update thread

Fedora

Fedora allows updating packages in stable distributions. You can expect all snapd releases to be updated within a week or two of the upstream release, following the usual testing and migration process. Due to ABI incompatibilities, differences in build configuration process and distribution policy snapd re-execution is not supported on Fedora.

Resources for developers:

• koschei (continuous integration)
• koji (build farm)
• bodhi (updates)
• source code
• 2.62 for F40
• 2.62 for F39
• 2.62 for F38

EPEL (RHEL, CentOS, Alma Linux, Rocky Linux, etc)

Snapd is not directly available in the Red Hat family of enterprise distributions. It is freely available and maintained in the commonly used EPEL (extra packages for enterprise linux) repository. You can expect all snapd releases to be updated within a week or two of the upstream release, following the usual testing and migration process. Due to ABI incompatibilities, differences in build configuration process and distribution policy snapd re-execution is not supported on any of those systems.

• 2.62 for EPEL9
• 2.62 for EPEL8
• 2.62 for EPEL7

openSUSE, SUSE Enterprise Linux

Snapd is not directly available in the openSUSE or SUSE archive. Instead the package is maintained in the system:snappy project in Open Build Service (OBS), making it easily installable on the family of related SUSE distributions. You can expect all snapd releases to be updated within a week of the upstream release. Due to ABI incompatibilities, differences in build configuration process and distribution policy snapd re-execution is not supported.

Resources for developers:

• system:snappy
• system:snappy/snapd source code
• OSB#1127366 include snapd in Factory WIP

Arch Linux

Snapd is available in the Arch User Repository (AUR). You can expect all snapd releases to be updated within a week of the upstream release. Due to ABI incompatibilities, differences in build configuration process, snapd re-execution is not supported.

Resources for developers:

• Package repo: snapd in AUR

Manjaro

Resources for developers:

• packaging repository packages/extra

Gentoo

Resources for developers:

• packaging repository app-containers/snapd

Solus

Snapd is available in the distribution archive. You may have to run extra commands to enable the snapd.socket and the snapd.apparmor.service. See TBD - installation instructions missing.

Resources for developers:

• packaging repository
• 2.61.1 update pull request
• 2.61.2 update pull request

Amazon Linux

Package repo: snapd-amazon-linux (unofficial)

Snapd upstream packaging: snapd upstream

Instructions Unofficial snapd repositories for Amazon Linux

Yocto layer

A Yocto meta-layer called meta-snapd exists, allowing the use of snapd and snaps on custom-build system images. Individual branches are named after Yocto release names.

Resources for developers

• 2.61.1 update thread

---

Last updated 21 days ago.