Remove LXD container once we've finished a build
Metadata
Current evaluation
Closed without merging. Testing confirmed containers are already destroyed, but the proposed cleanup logic fails because containers must be started first, which was previously broken. The approach was deemed unviable.
Suggested action: —
No scores available.
Issue body
There is no need to keep a container if we take a different name
each time we run a build anyway. Container construction is fast
and therefor we can just drop the container once we're done with it.
LP: #1570708
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without merging. Testing confirmed containers are already destroyed, but the proposed cleanup logic fails because containers must be started first, which was previously broken. The approach was deemed unviable. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. Maintainer noted containers are destroyed post-build but must be started first, which was failing. The proposed cleanup logic was insufficient for the current workflow. Acknowledged and thanked. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging. Maintainers noted containers are already destroyed post-build, but the PR logic fails due to broken container startup. Deferred pending underlying fixes. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1769 lxd: add an --image argument to cleanbuild | snapcraft | closed | Rejected and closed. Maintainers abandoned container-based builds in favor of VMs, rendering the LXD image argument obsolete. The PR was not merged. |