[Bug 1751249] Re: Using “content:” in gadget.yaml for a “role: system-data” partition makes it not be system-data anymore
Oliver Grawert
ogra at grawert.net
Fri Feb 23 12:49:45 UTC 2018
$ find build/unpack/gadget/writable/
build/unpack/gadget/writable/
build/unpack/gadget/writable/meep.txt
build/unpack/gadget/writable/system-data
build/unpack/gadget/writable/system-data/etc
build/unpack/gadget/writable/system-data/etc/foo.txt
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-image in Ubuntu.
https://bugs.launchpad.net/bugs/1751249
Title:
Using “content:” in gadget.yaml for a “role: system-data” partition
makes it not be system-data anymore
Status in ubuntu-image package in Ubuntu:
New
Bug description:
The core team thinks this is an ubuntu image bug, so i'm filing this
here additionally to
https://forum.snapcraft.io/t/using-content-for-a-role-system-data-
partition-makes-it-not-be-system-data-anymore
When i use a gadget.yaml entry like:
- name: writable
type: 83,0FC63DAF-8483-4772-8E79-3D69D8477DE4
filesystem: ext4
filesystem-label: writable
size: 270M
role: system-data
content:
- source: writable/
target: /
The partition is not pre-populated with snaps and seed but only the
files defined in content are copied in.
I would expect that the partition is still properly pre-populated with
the usual writable/system-data content and that the content from the
content: entry is additionally copied in place. Or at least that the
role: system-data takes precedence here if this combination is not
allowed (though snapcraft or ubuntu-image should then spill a warning
at least) so that a bootable system exists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1751249/+subscriptions
More information about the foundations-bugs
mailing list