Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update troubleshooting.md when Network Manager is running #1943

Merged
merged 2 commits into from
Apr 9, 2024
Merged

Update troubleshooting.md when Network Manager is running #1943

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4f29903
Update troubleshooting.md when Network Manager is running
keith-horton Apr 8, 2024
4de560c
Update troubleshooting.md
keith-horton Apr 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions WSL/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,6 +320,15 @@ WSL will automatically configure certain Linux networking settings when using mi

There is a known issue in which Docker Desktop containers with published ports (docker run –publish/-p) will fail to be created. The WSL team is working with the Docker Desktop team to address this issue. To work around the issue, use the host’s networking namespace in the Docker container. Set the network type via the "--network host" option used in the "docker run" command. An alternative workaround is to list the published port number in the `ignoredPorts` setting of the [experimental section in the WSL Configuration file](/windows/wsl/wsl-config#experimental-settings).

### Docker container issues when its Network Manager is running

There is a known issue with Docker containers which have the Network Manager service running. Sympoms include failures when trying to make loopback connections to the host.
keith-horton marked this conversation as resolved.
Show resolved Hide resolved
It's recommended to stop the Network Manager service for WSL networking to be configured properly:

```Bash
sudo systemctl disable network-manager.service
```

### DNS suffixes in WSL

Depending on the configurations in the .wslconfig file, WSL will have the following behavior wrt DNS suffixes:
Expand Down