Using “content:” in gadget.yaml for a “role: system-data” partition makes it not be system-data anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Image |
New
|
Undecided
|
Łukasz Zemczak | ||
ubuntu-image (Ubuntu) |
Confirmed
|
Undecided
|
Łukasz Zemczak |
Bug Description
The core team thinks this is an ubuntu image bug, so i'm filing this here additionally to
When i use a gadget.yaml entry like:
- name: writable
type: 83,0FC63DAF-
filesystem: ext4
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/
description: | updated |
summary: |
- Using “content:” in gadget.ymal for a “role: system-data” partition + Using “content:” in gadget.yaml for a “role: system-data” partition makes it not be system-data anymore |
Changed in ubuntu-image (Ubuntu): | |
assignee: | nobody → Łukasz Zemczak (sil2100) |
Changed in ubuntu-image: | |
assignee: | nobody → Łukasz Zemczak (sil2100) |
tags: | added: id-5aaae805ae59a6e226e8ad1b |
tags: | added: fr-470 |
building with -b ./build creates the following (the proper files from the gadget copied via "content:"):
$ find build/volumes/ beaglebone/ part3 beaglebone/ part3 beaglebone/ part3/meep. txt beaglebone/ part3/system- data beaglebone/ part3/system- data/etc beaglebone/ part3/system- data/etc/ foo.txt
build/volumes/
build/volumes/
build/volumes/
build/volumes/
build/volumes/