in the common case of networking issues between LXD and Docker, the error's doc_url isn't useful
Metadata
Current evaluation
Added LXD/Docker networking-conflict troubleshooting guidance, resolving the generic error documentation in PR #1148 (commit 7e896a30).
Resolution: closed resolved
Reason: PR #1148 updated the documentation to cover the LXD/Docker incompatibility workaround; the change was recorded in commit 7e896a30.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
When hitting the issue described here: https://documentation.ubuntu.com/lxd/en/latest/howto/network_bridge_firewalld/#prevent-connectivity-issues-with-lxd-and-docker, Rockcraft will raise an error similar to the following:
```
A network related operation failed in a context of no network access.
Recommended resolution: Verify that the environment has internet connectivity; see https://craft-providers.readthedocs.io/ for further reference.
```
But the given `doc_url` doesn't really have any useful information about how to fix this issue. It is too generic.
I understand networking issues can vary, but we should at least have a troubleshooting section as a "catch all", where this specific LXD vs Docker conflict is described as a potential solution to the error.
### To Reproduce
Start from a fresh installation, install Docker, setup LXD and then `rockcraft pack`.
### Environment
Any
### rockcraft.yaml
```shell
Any
```
### Relevant log output
```shell
A network related operation failed in a context of no network access.
Recommended resolution: Verify that the environment has internet connectivity; see https://craft-providers.readthedocs.io/ for further reference.
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Added LXD/Docker networking-conflict troubleshooting guidance, resolving the generic error documentation in PR #1148 (commit 7e896a30). | |
| stealth/space-bunny-alpha | — | closed resolved | Documentation now covers the LXD/Docker networking conflict and workaround, resolving the generic error guidance via PR #1148 (7e896a30). | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by updating documentation to include troubleshooting guidance for LXD and Docker networking conflicts. The issue was closed after the generic error message was supplemented with specific resolution steps. | |
| qwen/qwen3.6-35b-a3b | — | — | Documentation was updated to include troubleshooting steps for LXD and Docker networking conflicts, resolving the generic error message. The issue was closed after the fix was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by updating documentation to include troubleshooting steps for LXD and Docker networking conflicts. The generic error guidance was replaced with specific connectivity instructions, closing the issue. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Documentation updated to include a troubleshooting section for LXD and Docker networking conflicts. The generic error URL now directs users to specific resolution steps, addressing the reported lack of useful guidance. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/rockcraft#1148
(confidence 99%)
Merged documentation update committed as 7e896a30.
Related issues
No related issues found above the similarity threshold.