Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support snap parallel installs #411

Closed
lengau opened this issue Aug 12, 2024 · 3 comments · Fixed by #467
Closed

Support snap parallel installs #411

lengau opened this issue Aug 12, 2024 · 3 comments · Fixed by #467
Assignees
Labels
Enhancement New feature or request triaged

Comments

@lengau
Copy link
Contributor

lengau commented Aug 12, 2024

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

canonical/charmcraft#1770

@lengau lengau added Enhancement New feature or request triaged labels Aug 12, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3212.

This message was autogenerated

@dilyn-corner
Copy link

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.

@mr-cal
Copy link
Contributor

mr-cal commented Sep 16, 2024

Closing because this piece in craft-application is fixed, but we will likely run into the next issue in craft-providers.

The craft-providers fix is probably changing this line to snap_name.split('_')[0].

@mr-cal mr-cal closed this as completed Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants