Closed lengau closed 5 days ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3212.
This message was autogenerated
I mentioned a trivially reproducible case in the snapcraft matrix room, but I will cross-post it here for easy reference:
git clone -b split_kernel_initrd_plugins --depth 1 https://github.com/kubiko/snapcraft
cd snapcraft
snapcraft
snap install --dangerous --classic snapcraft_8*.snap snapcraft_kernel
cd ../
git clone -b 24-riscv64-nezha --depth 1 https://github.com/canonical/iot-field-kernel-snap
cd iot-field-kernel-snap
snapcraft_kernel
Error message you will receive:
Bad snapcraft.yaml content:
- plugin not registered: 'initrd' (in field 'parts.initrd')
snapcraft_kernel
is precisely the version of snapcraft which supports the initrd plugin -- the snapcraft installed as snapcraft
is actually the one being injected into the build environment.
What needs to get done
If the application is installed as a snap, we need to be able to copy that same parallel install's revision into the provider rather than the default (un-instanced) revision.
Why it needs to get done
https://github.com/canonical/charmcraft/issues/1770