Thanks to automatic updates, the tools that make up the snap ecosystem are constantly upgrading and evolving in the background, and this can make it difficult to track changes and new features as they appear.
Below, we outline some of the more significant recent changes to these snap-related tools and their associated documentation:
- Snap daemon: snapd, the core of the snap ecosystem, responsible for the day-to-day running, installation, management and removal of your snaps
- Snapcraft: the command line tool that easily builds snaps from a huge range of sources
- Documentation: where you’ll find everything from quickstart guides to in-depth technical specifications
The current stable version of snapd (the snap daemon) is 2.58, released 12th January 2023.
With the release of snapd 2.58, snap refreshes for all and specific snaps can now be delayed (or held, in our terminology) for any period of time, including indefinitely:
$ snap refresh --hold=24h Auto-refresh of all snaps held until 2022-10-26T14:25:58+01:00
For more details on holding updates, see Postpone updates with refresh hold.
The previous release included quota group support for journal log limits and the ability for snaps to be signed with an alternative delegated authority with their own constraints.
Previous releases in 2022 contain a lot of background engineering to support Ubuntu Core 22. However, there are a couple of user-facing features, including new support for starred developers and the ability to factory reset a device running Ubuntu Core.
Alongside support for side-loading multiple snaps via the API, and RISC-V support for snap’s security layer, the previous snapd release added a new shared-memory interface. This interface will help snap developers share messages and data between their snaps via the
/dev/shm shared memory device. The kernel-module-load interface is also new and is going to be most useful on embedded devices that need to control their hardware.
Other recent releases have also added significantly to snap’s interface list, including scsi-generic for accessing SCSI Generic (sg) devices, the polkit interface to help with authorisation, desktop-launch to launch snaps from other snaps, raw-input for accessing raw devices directly and the netlink-driver to help transfer data between kernel and user space.
Ubuntu Core remains a focus for snapd development, with new options for setting the swap size, kernel command line customisation (with UC20, UC22 and Grub gadgets), API support for recovery systems and extra snapctl commands to power-off a device after installation and for probing the system mode. These feature follow earlier developments to customise UC2x kernel command line arguments and to create a solution to avoid the need for synchronous kernel and DTB update on a Raspberry Pi, using the little-known (but powerful!) assumes keyword. See Changes in pi/pi-kernel DTB handling for further details.
Another new feature, an experimental gdbserver option, can help when a snap is crashing or not behaving as expected.
snap run --experimental-gdbserver test-snapd-tools-core18.echo "hello gdb"
The above compliments the
snap run --gdb option that can already be used to debug executables running within a snap environment. For more information, see gdbserver option.
The current stable version of Snapcraft is 7.2 (released 24th October 2022).
The 7.2 release includes the following highlights:
- Automatic linting with the
- Easy switching between LXD and Multipass build providers
- A new store authentication mechanism
In particular, Snapcraft now includes its own linter functionality when working with snaps using the
core22 base. Snapcraft linters run automatically when a snap is packed, and will report any detected errors unless otherwise disabled.
The 7.0 release marked the end of an initial process to rebuild our tools to work across a variety of projects, and many of the changes reflect that development work. This includes a new lifecycle and the introduction of Craft Parts as a generic cross-project mechanism for obtaining data from different sources.
The 5.0 release was a milestone that marked the end of a significant development cycle while adding several new and important features, including a new snapcraft metrics command, Metadata links added to snapcraft.yaml and the complete removal of legacy code.
In combination with recent changes to snapd, Validation sets can now be used to manage updates by listing specific snaps that are either required to be installed together or are permitted to be installed together on a device or system.
See Snapcraft release notes for a more detailed look at recent Snapcraft releases.
We recently finished a new Snapcraft quickstart guide to help new snap developers familiarise themselves with the process. But there’s also been new documentation on Quota groups, migrating from
core22 and Snapcraft linters.
The release of Ubuntu Core 22 (UC22) was accompanied by a glut of new documentation, including guides for the Raspberry Pi and Intel NUC. We also documented the remodelling process and provided a guide on using remodelling to upgrade a UC20 device to UC22. Another big part of this release, and the wider snap ecosystem, is the introduction of Quota groups. These allow you to set resource limits, such as memory or CPU usage, for a set of snaps.
New documentation has also tracked both snapd and Snapcraft releases, with documentation for all the new interfaces, a new interface template with examples, and new docs on Snapcraft metrics, Snap install modes and Super-privileged interfaces.
Before this, there were new pages on Validation sets and Customising UC20 kernel command line arguments. We also have new installation instructions for one of the latest and most rapidly evolving Linux distributions, Installing snap on Rocky Linux.
Now that Ubuntu 16.04 LTS has reached the end of its standard support period, we’ve documented the process of Snapcraft and Extended Security Maintenance to keep old snaps built with patched packages, plus there’s a new page on Migrating between bases to help updating those old snaps to newer bases.
Other recent updates include pages on Debugging snaps with snap try, Progressive releases, which enable you to deploy your snap in phases, and Package repositories to add extra package sources to your snap build.
We’ve also made some tentative first steps to produce a troubleshooting page to help users identify the most common issues and hopefully their solutions. And with the recent additions of Flutter and ROS (1 and 2) extensions, the list of Snapcraft extensions has grown enough to warrant a separate page, which we’ve called Supported extensions.
For snap developers, we’ve added a guide to help build Flutter applications, a page to describe the differences between Public, Private and Unlisted snaps, the technical details behind our Security policy and sandboxing, and some guidance for Debugging snaps. The latter has been expanded to include details on using the excellent (and snap embedded) gdb and gdbserver.
We’ve also added an example implementation and, some real-world example scripts, to the Add snap configuration documentation. This hopefully makes adding configurable options to your own snaps easier.
Most of this documentation can be collaboratively discussed and changed on the respective topic in the doc category of the Snapcraft forum. See the documentation guidelines if you’d like to contribute.
Last updated 27 days ago.