Our explanatory and conceptual guides are written to provide a better understanding of how snap and the snap daemon (snapd) work. They enable you to expand your knowledge and become better at both building snaps and getting the most out of the snap ecosystem.
How snaps work
Understand how snaps update automatically, and use revisions and transactional updates to mange risk and mitigate potential issues.
- Refresh awareness: How updates are handled when apps are running.
- Using channels: Understanding channels, tracks, risk-levels and branches.
- Revisions: The unique identify for each and every snap version.
- Transactional updates: Update a group of snaps together, or none at all.
- Snap performance: How snaps limit any performance overhead.
Interfaces
As you begin to use snaps more, interfaces can be used to carefully permit and limit access to resouces.
- All about interfaces: The permission system used to manage access to resources.
- Interface auto-connection: How snaps gain automatic access to resources.
- Interface hooks: A feature to help developers control what happens when an interface is used.
Security
Learn about how snaps use standard Linux security policies to isolate themselves from the system, and from each other.
- Security policies: How we use AppArmor, Seccomp and cgroups to secure snaps.
- Snap confinement: Learn more about snap’s various degrees of isolation.
- Assertions: Digitally signed documents used to verify all snap artefacts.
- Snapd release process: How and when we update the snapd package.
Last updated 2 days ago.