snap (package)

snap (package)
Name	snap
Title	snap (package)
Developer	Canonical Ltd.
Released	2014
Programming language	C++, Go, Python
Operating system	Linux
License	GNU GPL, other

snap (package)

snap (package) is a software packaging and deployment system for Linux developed by Canonical Ltd. It enables distribution of self-contained applications and services across multiple Linux distributions using transactional updates and sandboxed execution. The technology integrates with cloud platforms, desktop environments, and embedded systems, and competes with alternative packaging systems in the open source ecosystem.

Overview

snap provides a cross-distribution packaging mechanism intended to simplify application delivery across distributions such as Ubuntu, Debian, Fedora (Linux), openSUSE, and Arch Linux. It emphasizes atomic updates, rollback capability, and confinement via sandboxing primitives originally influenced by work at AppArmor and Linux kernel. The system includes a central distribution service, designed to interoperate with continuous integration systems used by organizations like Jenkins (software) and GitLab.

History and Development

snap was announced and initially developed by Canonical engineers associated with projects such as Ubuntu Touch and Snappy Ubuntu Core. Early work drew on concepts from containerization initiatives including LXC (Linux Containers) and orchestration efforts like Kubernetes. Development milestones were publicized at conferences such as Open Source Summit and through community channels involving maintainers from projects like Debian and GNOME. Over time, Canonical adjusted snap to address criticism from package maintainers in ecosystems represented by Red Hat and Arch Linux.

Architecture and Components

snap architecture comprises a runtime daemon, tooling, and metadata systems. The core components include the snapd background service, command-line tooling inspired by dpkg and APT (software), and a store backend modeled on package repositories such as Debian repository and Fedora Package Database. snapd interacts with kernel features such as namespaces and capabilities implemented by Linux kernel contributors and security modules like AppArmor and interacts with init systems including systemd. Build and packaging tooling integrate with continuous delivery platforms like Jenkins (software) and source code hosting services such as GitHub and GitLab.

Package Format and Metadata

snap packages are published as compressed squashfs archives that bundle application binaries, libraries, and metadata. The manifest format includes fields analogous to metadata used by Debian control files and RPM (file format) spec files, and supports interfaces for declaring plugs and slots similar in concept to Freedesktop.org specifications used by Flatpak and AppImage. Metadata enables dependency declarations, hooks for lifecycle events, and confinement profiles that map to policies in AppArmor or SELinux maintained by projects like NSA (U.S. National Security Agency) contributors in the broader ecosystem.

Distribution and Snap Store

Canonical operates the Snap Store as the primary distribution endpoint, analogous to vendor-run repositories like Google Play and Apple App Store in the mobile domain and enterprise repositories hosted by Red Hat. The Snap Store supports channels, revision management, and publisher accounts similar to mechanisms in Docker Hub and Amazon Web Services. Publishing workflows integrate with build pipelines from Travis CI and CircleCI and artifact registries like Artifactory. Community and third-party stores have been proposed by contributors from organizations such as Debian and KDE.

Security and Confinement

snap implements confinement using kernel namespaces, seccomp filters, and AppArmor profiles created by Canonical engineers collaborating with upstream Linux kernel maintainers. The model distinguishes between strict, classic, and devmode confinement levels, paralleling sandboxing strategies from SELinux and container runtimes like runc. snap interfaces for requesting permissions resemble permission systems in mobile platforms such as Android (operating system) and iOS. Security researchers from institutions like EFF and vendors such as Red Hat have evaluated snap's attack surface and sandbox effectiveness.

Reception and Criticism

snap has elicited mixed responses from the open source community. Advocates cite advantages similar to those promoted by proponents of Flatpak and AppImage: ease of distribution across distributions, transactional updates, and improved app availability on Ubuntu. Critics from projects including Debian and Fedora Project have raised concerns about centralization, store control, and integration with distribution packaging policies, echoing debates that involved stakeholders such as Linus Torvalds and maintainers of GNOME. Performance, disk usage, and startup time comparisons have been performed by independent groups and publications like Phoronix and discussed at venues such as LinuxCon.

Category:Linux software