Defining base snap breaks snapping Subiquity
Bug #1860550 reported by
Niek Wessels
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
New
|
Undecided
|
Unassigned | ||
snapd |
Invalid
|
Undecided
|
Unassigned | ||
subiquity |
Fix Released
|
High
|
Unassigned |
Bug Description
Subiquity basically uses an old snapcraft.yaml configuration. I updated this configuration to use base: core18 and multipass and set up all of its dependencies and packages to be local. When injecting the snap into an ISO, snapd gets stuck in "Wait until snapd is fully seeded". Checking back with TTY2, I see that the /snap/bin directory is empty. When not specifying a base keyword, the /snap/bin directory consists of the required snap parts and runs correctly.
summary: |
- Snapping Subiquity doesn't snap binaries + Defining core18 as base breaks snapping subiquity |
summary: |
- Defining core18 as base breaks snapping subiquity + Defining base snap breaks snapping Subiquity |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in subiquity: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
My own snapcraft.yaml