Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

An error occurred while submitting your form. Please try again or file a bug report. Close

  1. Blog
  2. Article

Jamie Bennett
on 1 June 2016

Apps to Snaps


Distributing applications on Linux is not always easy. You have different packaging formats, base systems, available libraries, and distribution release cadences all of which contribute to the headache. But now we have something much simpler: Snaps.

Snaps are a new way for developers to package their applications, bringing with it many advantages over the more traditional package formats such as .deb, .rpm, and others. Snaps are secure, isolated from each other and the host system using technologies such as AppArmor, they are cross-platform, and they are self-contained, allowing a developer to package the exact software their application needs. This sandboxed isolation also improves security and allows applications, and whole snap-based systems, to be rolled back should an issue occur. Snaps really are the future of Linux application packaging.

Creating a snap is not difficult. First, you need the snap-based runtime environment that is able to understand and execute snaps on your desktop; this tool is named snapd and comes as default on all Ubuntu 16.04 systems. Next you need the tool to create snaps, Snapcraft, which can be installed simply with:

$ sudo apt-get install snapcraft

Once you have this environment available it is time to get snapping.

Snaps use a special YAML formatted file named snapcraft.yaml that defines how the application is packaged as well as any dependencies it may have. Taking a simple application to demonstrate this point, the following YAML file is a real example of how to snap the moon-buggy game, available from the Ubuntu archive.

name: moon-buggy
version: 1.0.51.11
summary: Drive a car across the moon
description: |
A simple command-line game where you drive a buggy on the moon
apps:
play:
command: usr/games/moon-buggy
parts:
moon-buggy:
plugin: nil
stage-packages: [moon-buggy]
snap:
– usr/games/moon-buggy

The above code demonstrates a few new concepts. The first section is all about making your application discoverable in the store; setting the packaging metadata name, version, summary, and description. The apps section implements the play command which points to the location of the moon-buggy executable. The parts section tells Snapcraft about any required plugins that are needed to build the application along with any packages it depends on. In this simple example all we need is the moon-buggy application itself from the Ubuntu archive and Snapcraft takes care of the rest.

Running snapcraft in the directory where you have the snapcraft.yaml file will create the moon-buggy_1.0.51.11_amd64.snap which can be installed by running:

$ snap install moon-buggy_1.0.51.11_amd64.snap

To seen an example of snapping something a little more complex, like the Electron-based Simplenote application see here, for a tutorial online here and the corresponding code on GitHub. More examples can be found on the getting Ubuntu developer website here.

Related posts


Canonical
30 September 2025

Canonical achieves ISO 27001 certification

Canonical announcements Article

The certification demonstrates alignment with cybersecurity standards that will further safeguard open source products and services for use in the most demanding enterprise environments. Canonical is proud to announce it has achieved the ISO/IEC 27001 certification for its Information Security Management System (ISMS), following an extens ...


Jehudi
29 September 2025

Fortifying security for Ubuntu on Azure with Metadata Security Protocol (MSP)

Cloud and server Article

Ubuntu now supports Azure’s Metadata Security Protocol (MSP), raising the baseline for VM security on Azure. MSP locks down IMDS and WireServer behind HMAC-signed, identity-aware requests enforced by the azure-proxy-agent (Canonical’s integration of Microsoft’s GPA) using eBPF interception and per-endpoint allowlists. It must be enabled f ...


Stephanie Domas
24 September 2025

Beyond ‘whack-a-mole’ and insecticide

Ubuntu Article

Designing a new, robust, sustainable, and truly holistic approach to cybersecurity Talk to any cybersecurity expert or IT security manager, and they’ll tell you they’re sick of alerts and issues. For a while now, the industry has slowly been realizing that there’s a better way to improve cybersecurity and resolve security issues in IT wit ...