| Snap | |
| Logo Alt: | Snapcraft Logo |
| Programming Language: | Go, C, Shell script, Python, JavaScript, NASL[1] |
| Operating System: | Linux |
| License: | GNU GPLv3 (Client & Runtime), proprietary (Backend)[2] |
Snap is a software packaging and deployment system developed by Canonical for operating systems that use the Linux kernel and the systemd init system. The packages, called snaps, and the tool for using them, snapd, work across a range of Linux distributions[3] and allow upstream software developers to distribute their applications directly to users. Snaps are self-contained applications running in a sandbox with mediated access to the host system. Snap was originally released for cloud applications[4] but was later ported to also work for Internet of Things devices[5] [6] and desktop[7] [8] applications.
Applications in a Snap run in a container with limited access to the host system. Using Interfaces, users can give an application mediated access to additional features of the host such as recording audio, accessing USB devices and recording video.[9] [10] [11] These interfaces mediate regular Linux APIs so that applications can function in the sandbox without needing to be rewritten. Desktop applications can also use the XDG Desktop Portals, a standardized API originally created by the Flatpak project to give sandboxed desktop applications access to host resources.[12] [13] These portals often provide a better user experience compared to the native Linux APIs because they prompt the user for permission to use resources such as a webcam at the time the application uses them. The downside is that applications and toolkits need to be rewritten in order to use these newer APIs.
The Snap sandbox also supports sharing data and Unix sockets between Snaps.[14] This is often used to share common libraries and application frameworks between Snaps to reduce the size of Snaps by avoiding duplication.[15] [16]
The Snap sandbox heavily relies on the AppArmor Linux Security Module from the upstream Linux kernel. Because only one "major" Linux Security Module (LSM) can be active at the same time, the Snap sandbox is much less secure when another major LSM is enabled. As a result, on distributions such as Fedora which enable SELinux by default, the Snap sandbox is heavily degraded. Although Canonical is working with many other developers and companies to make it possible for multiple LSMs to run at the same time, this solution is still a long time away.[17] [18] [19]
The Snap sandbox prevents snapped desktop applications from accessing the themes of the host operating system to prevent compatibility issues. In order for Snaps to use a theme, it also needs to be packaged in a separate Snap. Many popular themes are packaged by the Snap developers[20] but some themes are not supported yet[21] and uncommon themes have to be installed manually. If a theme is not available as a Snap package, users have to resort to choosing the best matching theme available.[22] Work is ongoing to make it easier for third parties to package themes in a Snap and to automatically install uncommon system themes.[23]
Multiple times a day, snapd checks for available updates of all Snaps and installs them in the background using an atomic operation. Updates can be reverted[24] [25] and use delta encoding to reduce their download size.[26] [27] [28]
Publishers can release and update multiple versions of their software in parallel using channels. Each channel has a specific track and risk, which indicate the version and stability of the software released on that channel. When installing an application, Snap defaults to using the latest/stable channel, which will automatically update to new major releases of the software when they become available. Publishers can create additional channels to give users the possibility to stick to specific major releases of their software. For example, a 2.0/stable channel would allow users to stick to the 2.0 version of the software and only get minor updates without the risk of backwards incompatible changes. When the publisher releases a new major version in a new channel, users can manually update to the next version when they choose.[29] [30] [31] [32]
The schedule, frequency and timing of automatic updates can be configured by users. For example, this command will check for updates on the last Friday from 23:00 to 01:00.
| Snapcraft | |
| Logo Alt: | Snapcraft Logo |
| Repo: | github.com/snapcore/snapcraft |
| Programming Language: | Python, Shell script, C++, Go, Dart[38] |
| Operating System: | Linux |
Snapcraft is a tool for developers to package their programs in the Snap format.[39] It runs on any Linux distribution supported by Snap, macOS and Microsoft Windows.[40] Snapcraft builds the packages in a Virtual Machine using Multipass,[41] in order to ensure the result of a build is the same, regardless of which distribution or operating system it is built on.[42] Snapcraft supports multiple build tools and programming languages, such as Go, Java, JavaScript, Python, C/C++ and Rust. It also allows importing application metadata from multiple sources such as AppStream, git, shell scripts and setup.py files.[43] [44]
The Snap Store allows developers to publish their snap-packaged applications.[45] All apps uploaded to the Snap Store undergo automatic testing, including a malware scan. However, the scan does not catch all issues. In one case in May 2018, two applications by the same developer were found to contain a cryptocurrency miner which ran in the background during application execution. When this issue was found, Canonical removed the applications from the Snap Store and transferred ownership of the Snaps to a trusted third party which re-published the Snaps without the miner present.[46] [47] [48] Although the Snap sandbox reduces the impact of a malicious app, Canonical recommends users only install Snaps from publishers trusted by the user.[49] [50]
Snaps are self-contained packages that work across a range of Linux distributions. This is unlike traditional Linux package management approaches, which require specifically adapted packages for each Linux distribution.[51] [52]
The snap file format is a single compressed filesystem using the SquashFS format with the extension .snap. This filesystem contains the application, libraries it depends on, and declarative metadata. This metadata is interpreted by snapd to set up an appropriately shaped secure sandbox for that application. After installation, the snap is mounted by the host operating system and decompressed on the fly when the files are used.[53] Although this has the advantage that snaps use less disk space, it also means some large applications start more slowly.[54] [55]
A significant difference between Snap and other universal Linux packaging formats such as Flatpak is that Snap supports any class of Linux application such as desktop applications, server tools, IoT apps and even system services such as the printer driver stack.[56] [57] To ensure this, Snap relies on systemd for features such as running socket-activated system services in a Snap.[58] This causes Snap to work best only on distributions that can adopt that init system.[59]
Snap initially only supported the all-Snap Ubuntu Core distribution, but in June 2016, it was ported to a wide range of Linux distributions to become a format for universal Linux packages.[60] Snap requires Systemd which is available in most, but not all, Linux distributions. Other Unix-like systems (e.g. FreeBSD) are not supported.[61] ChromeOS does not support Snap directly, only through Linux distributions installed in it that support Snap, such as Gallium OS.[62]
Ubuntu and its official derivatives pre-install Snap by default, as well as other Ubuntu-based distributions such as KDE Neon, Solus, and Zorin OS.[63] Solus have currently planned to drop Snap, to reduce the burden of maintaining AppArmor patches needed for strict Snap confinement.[64] Zorin OS have removed Snap as a default package in the Zorin OS 17 release.[65] While other official Ubuntu derivatives such as Kubuntu, Xubuntu, and Ubuntu MATE have also shipped with the competing Flatpak as a complement, they will no longer do so beginning with Ubuntu 23.04, meaning that it must be installed manually by the user.[66]
A number of notable desktop software development companies publish their software in the Snap Store, including Google,[67] JetBrains,[68] KDE,[69] Microsoft (for Linux versions of e.g. .NET Core 3.1, Visual Studio Code, Skype,[70] and PowerShell), Mozilla[71] and Spotify.[72] Snaps are also used in Internet-of-Things environments, ranging from consumer-facing products[73] to enterprise device management gateways[74] and satellite communication networks.[75] [76] Finally, Snap is also used by developers of server applications such as InfluxDB,[77] Kata Containers,[78] Nextcloud[79] and Travis CI.[80]
Snap has received mixed reaction from the developer community. On Snap's promotional site, Heroku praised Snap's auto-update as it fits their fast release schedule well. Microsoft mentions its ease of use and Snap being YAML-based, as well as it being distribution-agnostic. JetBrains says the Snap Store gives their tools more exposure.[81]
Others have objected to the closed-source nature of the Snap Store. Clément Lefèbvre (Linux Mint founder and project leader[82] [83]) has written that Snap is biased and has a conflict of interest. The reasons he cited include it being governed by Canonical and locked to their store, and also that Snap works better on Ubuntu than on other distributions.[84] He later announced that the installing of Snap would be blocked by APT in Linux Mint,[85] [86] although a way to disable this restriction would be documented.[87]
On recent versions of Ubuntu, Canonical has migrated certain packages exclusively to Snap, such as Chromium and Firefox[88] web browsers.[89] The replacement of Firefox led to mixed reception from users due to performance issues with the Snap version, especially on startup.