Skip to content

focal/hooks: snapd enablement, Round 2

Alfred Neumayer requested to merge personal/fredldotme/snap-round2 into master

  • Snaps can ship with daemons and services doing privilege separation themselves, by means of using a well-known user(id) and dropping privleges from there. Create those users and groups in the respective default databases in /etc for snapd to consume and use those as it sees appropriate. Note that albeit one of them is marked as deprecated, we should keep it for proper support of yet-to-be adapted snap packages.

  • Add VARIANT and VARIANT_ID in /etc/os-release for distinction purposes. Right now snapd's checks result in Ubuntu Touch being detected as classic, where as it is actually a hybrid between Classic and Core. Rootfs layout is in line with Classic but the readonly nature (and very similar writable-paths mechanisms) cause it to fail in situations where Classic would pass.
    With this change (similarly to how other types like Core Desktop and WSL are detected) snapd can distinguish between Classic and Touch and adapt its behavior appropriately, as in the case of creating new users and groups in the "extrausers" database.

Merge request reports