feat(ProviderService): don't inject snaps if the host and guest architectures differ
Metadata
Current evaluation
Merged PR #1037 as commit 16bd7ac3, preventing host application-snap injection for cross-architecture guests and using Snap Store installation instead.
Resolution: closed resolved
Reason: PR #1037 was approved, passed all CI checks, and merged as commit 16bd7ac3. It changes ProviderService to install the application snap from the Snap Store when host and guest architectures differ.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Update ProviderService snap setup so that when the requested provider/
container architecture differs from the host, the application snap is installed
from the Snap Store instead of being injected from the host snap (avoiding
cross-arch injection issues).
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `make lint && make test`?
- [ ] Have you added an entry to the changelog (`docs/reference/changelog.rst`)?
---
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #1037 as commit 16bd7ac3, preventing host application-snap injection for cross-architecture guests and using Snap Store installation instead. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged canonical/craft-application#1037: ProviderService now installs application snaps from the Snap Store instead of host-injecting them when host and guest architectures differ. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged. Updates ProviderService to install application snaps from the Snap Store instead of injecting them from the host when architectures differ, preventing cross-arch injection issues. Approved by two reviewers with all CI checks passing. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged ProviderService updates that prevent cross-architecture snap injection. When host and guest architectures differ, the application snap is now fetched from the Snap Store instead of being injected from the host snap, resolving compatibility issues. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-application#1027
(confidence 95%)
Merged in commit 15f48281 and enabled builds for other compatible architectures, providing the cross-architecture context for #1037.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2174 build_providers: inject snaps when running from a snap | snapcraft | merged | Merged PR #2174 (commit 283ab0bb8) to inject host Snapcraft and base snaps when running from the snapcraft snap, while non-snap runs install them from the store. | |
| #1064 fix: skip injecting snaps from host when cross-building | craft-application | closed | Closed as redundant after the same cross-build snap-injection fix merged in canonical/craft-application#1037 via commit 16bd7ac3. | |
| #1059 Packing with CRAFT_BUILD_ON can fail when installing registered snaps | craft-application | open | Cross-architecture packing with registered snaps could inject incompatible host snaps; commit 16bd7ac3 now skips host snap injection when architectures differ. | |
| #444 feat(snaps): inject base snap from host | craft-providers | merged | Merged PR #444 in commit 03704c1, injecting each host snap's base snap and reusing an existing base; released in craft-providers 1.20.0. |