snapcraft.yaml syntax docs missing ‘classic’ confinement mode

Bug #1654899 reported by Chris Halse Rogers on 2017-01-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Medium
Unassigned

Bug Description

https://github.com/snapcore/snapcraft/blob/master/docs/snapcraft-syntax.md says:

confinement (string) The type of confinement supported by the snap. Can be either "devmode" (i.e. this snap doesn't support running under confinement) or "strict" (i.e. full confinement supported via interfaces).

I see from canonical-tech@ and some other merge requests that there's at least one other confinement mode, “classic”. The docs should probably mention it :)

Changed in snapcraft:
status: New → Confirmed
importance: Undecided → Medium
Leo Arias (elopio) wrote :

This is not yet working on the snapd side, so we shouldn't document it yet. But thanks for the bug report, we'll document it as soon as it works end-to-end.

tags: added: snap-docs
Sergio Schvezov (sergiusens) wrote :

Yes it does, I am a little confused by the experience though

sergiusens@lindon:~$ snap install vim --edge
error: cannot install "vim": snap not found
sergiusens@lindon:~$ snap install vim --edge --classic
vim (edge) 8.0 from 'sergiusens' installed

If this is the expected behavior I will have to share the `--classic` part where instead I want folks to be prompted about its implications.

In any case, the docs are going to be updated.

Gustavo Niemeyer (niemeyer) wrote :

This is being fixed. It should say something like:

error: snap %q requires unconfined access to the whole system - use --classic to proceed anyway

This follow up should be a new bug since the purpose of the original bug report has been fixed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers