docs: Add Windows WSL2 IPv6 troubleshooting guidance - #317
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5d70177238
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### Windows/WSL2 IPv6 troubleshooting | ||
|
|
||
| If a Windows local deployment fails with SSH connection resets or timeouts, force Podman’s SSH connection to use IPv4. Add this to `%USERPROFILE%\.ssh\config`: |
There was a problem hiding this comment.
Because this addition instructs Windows users to change their SSH configuration to operate or troubleshoot local deployments, it meets the explicit changelog threshold in CONTRIBUTING.md:36 for documentation that changes how users operate the tool. Add a corresponding entry under CHANGELOG.md’s Unreleased section so the workaround is included in the user-facing release history.
AGENTS.md reference: AGENTS.md:L11-L13
Useful? React with 👍 / 👎.
| Host * | ||
| AddressFamily inet |
There was a problem hiding this comment.
For Windows users who also connect to IPv6-only SSH hosts, Host * applies AddressFamily inet to every SSH destination, not only Podman, so following this workaround breaks those unrelated connections. This can be confirmed with OpenSSH configuration expansion: ssh -G -F <config> example.com reports addressfamily inet for an arbitrary host with this stanza. Scope the override to Podman’s connection or explain that users must remove it after troubleshooting.
Useful? React with 👍 / 👎.
|
moben
left a comment
moben
left a comment
There was a problem hiding this comment.
Wait, this causes deployment failure? My understanding earlier was that this is about manual ssh. Do we do ssh anywhere?
Does podman run itself work in this setup? If yes, what actually fails?
2 participants
Description
Adds concise Windows/WSL2 IPv6 troubleshooting guidance for local deployments.
Type of Change
feat: New featurefix: Bug fixdocs: Documentation updatetest: Test additions or changesrefactor: Code refactoringchore: Maintenance tasksChanges Made
Testing
task all)Checklist
task fmtandtask lintCHANGELOG.mdfor user-facing changes, including examples for new features when useful