Packaging Apps To Run on Any Linux Device

It's a Snap!

To dev or Not to dev

Developer mode (devmode ) offers a much looser set of controls, in the sense that, rather than actions being blocked, warnings are sent to Syslog (usually into one of the /var/log/messages or /var/log/syslog files, depending on the distribution). Some detail in the debugging documentation [7] explains that you should always add the --devmode option explicitly when you install a snap for sandbox work – even if you've loosened your security confinement settings within your YAML configuration file (snapcraft.yaml).

It's a Classic

To run a snap in a no-holds-barred, throwing-caution-to-the-wind mode, you select --classic, wherein the snap treats the host resources as its own. In the Snap Store, where a full catalog of snaps can be downloaded, any snaps set to run in classic mode are scrutinized by a human for safety reasons. I'll look in-depth about how you can develop your apps in classic mode in a moment.

Automatic Updates

Automatic updates are a natty addition. In the background, the current version of your snaps are checked against the latest versions and then updated if required on a daily basis. You can also use the refresh option to make sure you have the latest versions.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy ADMIN Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Container Apps
    Canonical’s Snapcraft (Snappy) package manager creates self-contained applications that work across Linux distributions. We show you how to install, publish, and run a simple snap.
  • Flatpak, Snap, and AppImage
    The Flatpak, Snap, and AppImage package formats work across distributions, but each has its specific disadvantages.
  • Zero-Ops Kubernetes with MicroK8s
    A zero-ops installation of Kubernetes with MicroK8s operates on almost no compute capacity and roughly 700MB of RAM.
comments powered by Disqus