Pre-built apps

Shipping a zip file or tarball of your app makes it easy for users to get started without the heavy lifting of you independently packaging for each Linux distribution.

However, this still requires that you provide instructions on installing your app’s dependencies and it requires that you come up with your own method for notifying users of available updates.

Snaps address these gaps while building upon the work you’ve already done to produce a release of your app.

Why are snaps good for pre-built apps?

  • Snaps are easy to discover and install
    Millions of users can browse and install snaps graphically in the Snap Store or from the command-line.
  • Snaps install and run the same across Linux
    They bundle the exact version of anything required, along with all of your app’s dependencies, be they executables or system libraries.
  • Snaps automatically update to the latest version
    Four times a day, users’ systems will check for new versions and upgrade in the background.
  • Upgrades are not disruptive
    Because upgrades are not in-place, users can keep your app open as it’s upgraded in the background.
  • Upgrades are safe
    If your app fails to upgrade, users automatically roll back to the previous revision.

Build a snap in 20 minutes

Ready to get started? By the end of this guide, you’ll understand how to make a snap of your app that can be published in the Snap Store, showcasing it to millions of Linux users.

:information_source: For a brief overview of the snap creation process, including how to install snapcraft and how it’s used, see Snapcraft overview. For a more comprehensive breakdown of the steps involved, take a look at Creating a snap.

Getting started

Snaps are defined in a single YAML file placed in the root folder of your project. The following example shows the entire snapcraft.yaml file for an existing project, Geekbench 4. Don’t worry, we’ll break this down.

name: test-geekbench4
version: 4.2.0
summary: Cross-Platform Benchmark
description: |
  Geekbench 4 measures your system's power and tells
  you whether your computer is ready to roar. How
  strong is your mobile device or desktop computer?
  How will it perform when push comes to crunch?
  These are the questions that Geekbench can answer.
confinement: devmode
base: core18

parts:
  test-geekbench4:
    plugin: dump
    source: http://cdn.geekbench.com/Geekbench-$SNAPCRAFT_PROJECT_VERSION-Linux.tar.gz

apps:
  test-geekbench4:
    command: geekbench4

Metadata

The snapcraft.yaml file starts with a small amount of human-readable metadata, which usually can be lifted from the GitHub description or project README.md. This data is used in the presentation of your app in the Snap Store.

name: test-geekbench4
version: 4.2.0
summary: Cross-Platform Benchmark
description: |
  Geekbench 4 measures your system's power and tells
  you whether your computer is ready to roar. How
  strong is your mobile device or desktop computer?
  How will it perform when push comes to crunch?
  These are the questions that Geekbench can answer.

The name must be unique in the Snap Store. Valid snap names consist of lower-case alphanumeric characters and hyphens. They cannot be all numbers. They also cannot start or end with a hyphen.

The summary can not exceed 79 characters. You can use a chevron ‘>’ in the description key to declare a multi-line description.

Base

The base keyword defines a special kind of snap that provides a run-time environment with a minimal set of libraries that are common to most applications. They’re transparent to users, but they need to be considered, and specified, when building a snap.

base: core18

core18 is the current standard base for snap building and is based on Ubuntu 18.04 LTS.

Security model

The next section describes the level of confinement applied to your app.

confinement: devmode

Snaps are containerised to ensure more predictable application behaviour and greater security. Unlike other container systems, the shape of this confinement can be changed through a set of interfaces. These are declarations that tell the system to give permission for a specific task, such as accessing a webcam or binding to a network port.

It’s best to start a snap with the confinement in warning mode, rather than strictly applied. This is indicated through the devmode keyword. When a snap is in devmode, runtime confinement violations will be allowed but reported. These can be reviewed by running journalctl -xe.

Because devmode is only intended for development, snaps must be set to strict confinement before they can be published as “stable” in the Snap Store. Once an app is working well in devmode, you can review confinement violations, add appropriate interfaces, and switch to strict confinement.

Parts

Parts define what sources are needed to assemble your app. Parts can be anything: programs, libraries, or other needed assets. For now, we just have one part: a tarball containing the geekbench binary.

parts:
  test-geekbench4:
    plugin: dump
    source: http://cdn.geekbench.com/Geekbench-$SNAPCRAFT_PROJECT_VERSION-Linux.tar.gz

The dump plugin unpacks the file specified in the source field and includes the contents in the snap. The source can be a local or remote zip file, deb file, or tarball.

In this example we use the $SNAPCRAFT_PROJECT_VERSION variable derived from the version: stanza in the metadata section to reference the release tarball.

Apps

Apps are the commands you want to expose to users and any background services your application provides. Each key under apps is the command name that should be made available on users’ systems.

The command specifies the path to the binary to be run. This is resolved relative to the root of your snap contents and automatically searches in the usr/sbin, usr/bin, sbin, and bin sub-directories of your snap.

apps:
  test-geekbench4:
    command: geekbench4

If your command name matches the snap name, users will be able run the command directly. If the names differ, then apps are prefixed with the snap name (geekbench4.command-name, for example). This is to avoid conflicting with apps defined by other installed snaps.

You can request an alias on the Snapcraft forum if your command name and snap name do not match but you don’t want your command prefixed. These aliases are set up automatically when your snap is installed from the Snap Store.

Building the snap

You can download the example repository with the following command:

$ git clone https://github.com/snapcraft-docs/geekbench4

After you’ve created the snapcraft.yaml, you can build the snap by simply executing the snapcraft command in the project directory:

$ snapcraft
Using 'snapcraft.yaml': Project assets will be searched for from the 'snap' directory.
Launching a VM.
[...]
Snapped test-geekbench4_4.2.0_amd64.snap

The resulting snap can be installed locally. This requires the --dangerous flag because the snap is not signed by the Snap Store. The --devmode flag acknowledges that you are installing an unconfined application:

$ sudo snap install test-geekbench4_*.snap --devmode --dangerous

You can then try it out:

$ test-geekbench4

Removing the snap is simple too:

$  sudo snap remove test-geekbench4

You can also clean up the build environment, although this will slow down the next initial build:

$ snapcraft clean

Publishing your snap

To share your snaps you need to publish them in the Snap Store. First, create an account on the dashboard. Here you can customise how your snaps are presented, review your uploads and control publishing.

You’ll need to choose a unique “developer namespace” as part of the account creation process. This name will be visible by users and associated with your published snaps.

Make sure the snapcraft command is authenticated using the email address attached to your Snap Store account:

$ snapcraft login

Reserve a name for your snap

You can publish your own version of a snap, provided you do so under a name you have rights to. You can register a name on dashboard.snapcraft.io, or by running the following command:

$ snapcraft register mysnap

Be sure to update the name: in your snapcraft.yaml to match this registered name, then run snapcraft again.

Upload your snap

Use snapcraft to push the snap to the Snap Store.

$ snapcraft push --release=edge mysnap_*.snap

If you’re happy with the result, you can commit the snapcraft.yaml to your GitHub repo and turn on automatic builds so any further commits automatically get released to edge, without requiring you to manually build locally.

Congratulations! You’ve just built and published your first pre-built binary snap. For a more in-depth overview of the snap building process, see Creating a snap.

Last updated 6 months ago. Help improve this document in the forum.