docs: Update handling of LXD/Docker incompatibility
Metadata
Current evaluation
Documentation updates for LXD/Docker incompatibility were implemented in PR #1148. The issue was closed as superseded by the merged pull request, which added sysctl configuration steps, linked official LXD docs, and updated warning admonitions.
Suggested action: —
No scores available.
Issue body
### Check existing issues
- [x] I've verified that this request isn't described by any existing issues.
### Request
We need to add the following steps to the setup instructions, after LXD has been set up but before Docker is installed:
```
echo "net.ipv4.conf.all.forwarding=1" \
| sudo tee -a /etc/sysctl.d/99-forwarding.conf
sudo systemctl restart systemd-sysctl
```
We also need to:
- Include the link to the [LXD documentation](https://documentation.ubuntu.com/lxd/stable-5.21/howto/network_bridge_firewalld/#prevent-connectivity-issues-with-lxd-and-docker) about the known issue.
- Add a warning admonition that in a production environment you should have a hardened firewall configuration.
- Remove the warning admonition under the first rock-packing with the alternate method.
### Related issues and PRs
#598 #1110
### Document location
https://documentation.ubuntu.com/rockcraft/latest/tutorial/
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Documentation updates for LXD/Docker incompatibility were implemented in PR #1148. The issue was closed as superseded by the merged pull request, which added sysctl configuration steps, linked official LXD docs, and updated warning admonitions. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged via PR #1148. Documentation was updated to include sysctl forwarding steps, link to LXD compatibility notes, and adjust warning admonitions as requested. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved via PR #1148. Documentation was updated to include sysctl forwarding steps, upstream LXD compatibility links, and revised warning admonitions for the LXD/Docker setup process. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as superseded by merged PR #1148. The pull request implemented the requested documentation updates, adding the sysctl forwarding configuration, linking to official LXD documentation, and adjusting warning admonitions for the LXD/Docker incompatibility. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
15
Complexity:
10
Confidence:
90
Support Request:
0
|
keep open | Documentation update adding sysctl forwarding steps and firewall warnings to resolve LXD and Docker network incompatibility. PR #1148 addresses the request and is currently under review. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1148 docs: update LXD/Docker incompatibility handling | rockcraft | merged | Merged documentation update adding LXD/Docker connectivity workaround and firewall warning to shared setup instructions. Iteratively resolved CI failures, docs build errors, and stale intersphinx mappings before final merge. Closes #1144. | |
| #1061 docs: Update LXD/Docker warning block in 12-factor tutorials | rockcraft | merged | Merged update clarifying LXD/Docker connectivity workarounds in 12-factor tutorials. Changes reposition network bridge instructions, add an environment variable for bridge names, and include sudo. Approved by three reviewers and merged. | |
| #598 in the common case of networking issues between LXD and Docker, the error's doc_url isn't useful | rockcraft | closed | 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. | |
| #1110 docs: reuse LXD/Docker networking troubleshooting snippet | rockcraft | closed | Superseded by PR #1144. Maintainers closed this PR after discussions determined an alternative approach better addresses the LXD/Docker networking troubleshooting duplication. The contributor was invited to continue work on the new PR. |