prefer "core" rather than "ubuntu-core" if installed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snap-confine |
Fix Released
|
Critical
|
Zygmunt Krynicki | ||
| snap-confine (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
snap-confine uses the "core" snap as the root filesystem of the environment where snap applications execute. In the past that was always "ubuntu-core". The core snap has now been renamed to just "core" and snap-confine needs to handle this case gracefully.
If both snaps are preset (core and ubuntu-core) then core is preferred and used. The apparmor profile was adjusted so that both "core" and "ubuntu-core" names are allowed and internally the code uses two new functions to find the location of the preferred core snap (one in the internal filesystem layout and one in the external filesystem layout)
For more information about the execution environment, please see this article http://
[Test Case]
The test case can be found here:
https:/
The test case is ran automatically for each pull request and for each final release. It can be reproduced manually by executing the shell commands listed in the prepare/
The commands there assume that snapd and snap-confine are installed.
No other additional setup is necessary.
[Regression Potential]
* Regression potential is minimal and mainly depends on what is published to the store as the "core" snap. If the core snap would somehow contain totally bogus content then obviously snaps would cease to work correctly.
[Other Info]
* snap-confine is technically an integral part of snapd which has an SRU exception and is allowed to introduce new features and take advantage of accelerated procedure. For more information see https:/
== # Pre-SRU bug description follows # ==
The system may run with more than one core snap, by default all snaps should run against the "core" snap but for compatibility the system should fall back to the "ubuntu-core" snap.
| summary: |
- IT DOESN'T WORK + prefer "core" rather than "ubuntu-core" if installed |
| description: | updated |
| Changed in snap-confine: | |
| milestone: | none → 1.0.43 |
| Changed in snap-confine: | |
| milestone: | 1.0.43 → 1.0.42.1 |
| status: | Triaged → Fix Released |
| description: | updated |
| Andy Whitcroft (apw) wrote Please test proposed package | #1 |
| Changed in snap-confine (Ubuntu Xenial): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in snap-confine (Ubuntu): | |
| status: | New → Fix Released |
| tags: |
added: verification-done removed: verification-needed |
| John Lenton (chipaca) wrote | #3 |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in snap-confine (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Steve Langasek (vorlon) wrote Update Released | #5 |
Hello John, or anyone else affected,
Accepted snap-confine into xenial-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-
Further information regarding the verification process can be found at https:/