Only load the project code on the to-build host
Metadata
Current evaluation
Fixed via snapcraft/snapcraft#2222 (commit b2bd6b776), associated with Launchpad #1788667, updating LXD snap injection for remote builds.
Resolution: closed resolved
Reason: Maintainer Sergius Enriquez reported that the issue was fixed as part of Launchpad #1788667. The implementation landed through snapcraft/snapcraft#2222 as commit b2bd6b776, adding new-style LXD snap injection.
Evaluated by: mr-cal-bot
No scores available.
Issue body
If we are going to dispatch a lifecycle execution onto a different host we don't need to load all the plugin code.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed via snapcraft/snapcraft#2222 (commit b2bd6b776), associated with Launchpad #1788667, updating LXD snap injection for remote builds. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed cleanbuild snap injection via snapcraft#1788667, delivered in canonical/snapcraft#2222 (commit b2bd6b776). | |
| stealth/space-bunny-alpha | — | closed stale | Closed without implementation: no PR or commit recorded for loading project code only on the build host. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The optimization to load project code only on the build host was not addressed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The optimization to skip loading plugin code on non-building hosts was abandoned or superseded by subsequent changes. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without discussion. The proposal to avoid loading plugin code on the dispatch host for remote lifecycle executions was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation or discussion. The optimization to skip loading plugin code on remote build hosts was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1788667
(confidence 100%)
The maintainer explicitly cited this Launchpad bug as where the issue was fixed.
-
Likely Fixed By:
snapcraft/snapcraft#2222
(confidence 98%)
Merged PR containing the resolving LXD remote-build changes in commit b2bd6b776.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1599578 Snapcraft cloudbuild | snapcraft (launchpad) | closed | Remote building was implemented by merged PR canonical/snapcraft#1121 (commit 834c24bb6), adding cleanbuild --remote for LXD hosts; PR #2500 later added Launchpad remote builds. | |
| #1364 lxd: Inject snapcraft and core snaps into the container | snapcraft | merged | Merged PR #1364 as 99f5598ac, injecting the host's Snapcraft and core snaps into LXD containers so builds no longer use a mismatched Xenial archive version. |