many: remove support for remote lxd per project containers
Metadata
Current evaluation
Merged #2089 (commit a3bafbb7c), removing remote LXD per-project container support due to poor UX and directing users to cleanbuild.
Resolution: closed resolved
Reason: Pull request #2089 was merged as commit a3bafbb7c. It removed the remote LXD workflow because it had not proved to be a good experience and recommended cleanbuild instead.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Remove the support as it has not proved to be the best experience, cleanbuild should be used
instead.
Also future feature proof the environment detection.
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)?
- [x] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)?
- [x] Have you successfully run `./runtests.sh static`?
- [x] Have you successfully run `./runtests.sh unit`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #2089 (commit a3bafbb7c), removing remote LXD per-project container support due to poor UX and directing users to cleanbuild. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2089 in a3bafbb7c, removing remote LXD per-project containers because of poor UX and directing users to cleanbuild instead. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #2089 (commit a3bafbb7c), removing remote LXD per-project containers because of poor UX and recommending cleanbuild instead. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/snapcraft#2089 (commit a3bafbb7c), removing remote LXD per-project container support after it proved unsuitable; cleanbuild is now the recommended approach. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged removal of remote LXD per-project container support due to poor user experience, recommending cleanbuild instead. Environment detection was future-proofed. Approved, passed CI, and modified 13 files. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged removal of remote LXD per-project container support due to poor user experience. Users should use cleanbuild instead. Environment detection was also future-proofed. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#1457
(confidence 99%)
Originating remote per-project container issue; its support was removed by #2089.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1457 remote per-project container | snapcraft | closed | Remote per-project LXD builds were implemented in #1302 (0e89c85ba), improved by #1847, then removed in #2089 (a3bafbb7c) because of poor UX. | |
| #2335 lifecycle: remove lxd support for bases | snapcraft | merged | Merged PR #2335 as commit 27ec9ba63, removing lifecycle LXD builds for projects using bases while retaining cleanbuild/LXD for non-base projects. | |
| #57 lxd launcher: enable configuration of project & remote (CRAFT-304) | craft-providers | merged | Merged PR #57 added configurable LXD project and remote support, with updated unit tests and new integration coverage; implemented in commit b420280. |