Docs: Multiple errors related to build provider installation
Metadata
Current evaluation
Docs errors fixed by merged PR #5537 (commit 6ac28562d): sudo and the user-group step were dropped and LXD init corrected to `sudo lxd init --auto`; core20-only resource tip kept.
Resolution: closed resolved
Reason: PR #5537 'docs: update build provider procedures' was merged as commit 6ac28562d and explicitly fixes #5519, removing the unnecessary sudo/user-group steps and fixing the LXD init command. The core20 hardware-resource tip was retained after a maintainer note that only core20 supports those variables (craft-providers#531).
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
In [Set up Snapcraft](https://documentation.ubuntu.com/snapcraft/stable/how-to/setup/set-up-snapcraft/), users have reported:
- [x] sudo isn't needed for Snapcraft installation.
- [ ] ~~The tip about increasing hardware capacity probably shouldn't be limited to core20.~~
- [ ] The _Install Multipass_ section implies that Multipass is always installed automatically. We must reinforce that that fact only applies to core20.
- [x] In the manual installation instructions for LXD:
- ~~The user group step is unneeded.~~
- The configuration step should be `sudo lxd init --auto`.
~~For the [tutorial](https://documentation.ubuntu.com/snapcraft/stable/tutorials/craft-a-snap):~~
- [ ] ~~Since LXD installation is automatic, the instructions for installing LXD are unneeded.~~
### To Reproduce
-
### Environment
-
### snapcraft.yaml
```yaml
-
```
### Relevant log output
```shell
-
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Docs errors fixed by merged PR #5537 (commit 6ac28562d): sudo and the user-group step were dropped and LXD init corrected to `sudo lxd init --auto`; core20-only resource tip kept. | |
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft installation docs were corrected in canonical/snapcraft#5537 (commit 6ac28562d): sudo and the user-group step were removed, and LXD initialization was fixed. The core20-only resource note remained. | |
| qwen/qwen3.6-35b-a3b | — | — | Documentation updates applied to correct sudo usage and LXD configuration steps. Hardware capacity tips and tutorial LXD instructions were abandoned after maintainers confirmed core22+ build providers lack support for those configurations. Issue closed. | |
| qwen/qwen3.6-35b-a3b | — | — | Documentation errors for Snapcraft build provider installation were triaged. A technical limitation was confirmed, clarifying resource configuration only applies to core20. The report was closed after internal ticket creation. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed via documentation updates correcting installation steps. A core22+ build provider limitation was confirmed, with remaining items addressed. Issue closed following revisions and technical clarification. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/snapcraft#5537
(confidence 95%)
Merged docs PR referencing #5519; commit 6ac28562d.
-
Related To:
canonical/craft-providers#531
(confidence 70%)
Cited by mr-cal as the reason the core20-only resource-tuning tip cannot be generalised.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5537 docs: update build provider procedures | snapcraft | merged | Merged PR #5537 in commit 6ac28562d, updating build-provider docs to remove sudo/user-group steps and correct LXD initialization; fixes #5519. | |
| #3052 build providers: wait for systemd and better nameserver setup on LXD | snapcraft | merged | PR #3052 merged as commit 7faeb2591: LXD build providers now wait for systemd to be running or degraded and prefer systemd-resolved's local nameserver; core20 provider tests enabled. |