Output a nice error message when docker breaks lxd
Metadata
Current evaluation
LXD launch timeouts lack guidance when Docker has changed firewall forwarding rules, despite a known iptables workaround being used in Spread configuration
Suggested action: needs triage
Reason: The report identifies the common timeout and points directly to the mitigation, while current spread.yaml and spread-docs.yaml explicitly set "iptables -P FORWARD ACCEPT" for Docker/LXD networking. However, no user-facing diagnostic was found, and the issue has no labels, comments, reproducer, or maintainer assessment clarifying which timeout path and LXD failure signature should trigger the message.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
13
Complexity:
47
Confidence:
88
Actionability:
63
Issue body
### What needs to get done
Instead of just timing out, suggest to do this stuff:
https://github.com/canonical/charmcraft/blob/main/spread.yaml#L192
### Why it needs to get done
Because this is a common issue whose solution is undocumented
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
13
Complexity:
47
Confidence:
88
Actionability:
63
|
needs triage | LXD launch timeouts lack guidance when Docker has changed firewall forwarding rules, despite a known iptables workaround being used in Spread configuration | |
| ~deepseek/deepseek-pro-latest |
Impact:
40
Quick Win:
12
Complexity:
45
Confidence:
60
Actionability:
55
|
needs triage | Feature request: emit a helpful error message when Docker's iptables changes break LXD networking (currently a silent timeout), pointing users to the iptables FORWARD ACCEPT fix. Unlabelled, no comments, no implementation. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
17
Complexity:
20
Confidence:
70
Actionability:
70
|
keep open | Improve error messages when Docker conflicts with LXD in spread tests. Currently times out without guidance. References spread.yaml:192 for LXD setup steps. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
26
Staleness:
65
Complexity:
25
Confidence:
72
Support Request:
10
|
needs triage | Feature request to print a helpful error message when Docker breaks LXD (suggesting iptables -P FORWARD ACCEPT), instead of just timing out. Created by maintainer lengau, no labels, no comments, no assignee, 1028 days old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
10
|
close stale | Feature request to improve error messaging when Docker interferes with LXD. Open with no maintainer comments or labels after nearly 3 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to replace generic timeouts with actionable guidance when Docker interferes with LXD. Currently open, unlabelled, and inactive for over 10 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
close stale | Feature request to improve error messaging when Docker interferes with LXD, suggesting a documented workaround instead of a timeout. Currently unlabelled and inactive for over 320 days. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.