cu0ngpitt
October 19, 2025, 1:00am
3
Oh wow, yea… exact same issue.
I am on Win 10 and there was an update my PC did on the day this issue was noticed which was 10/15/2025. I just tried and unfortunately I cannot roll back before the 10/15/2025 update
I do think this is related to some weird behavior from WSL. It doesn’t sound like I’m not going to be able to fix this unless Windows does and given I’m on a deprecated version they will likely not help me. We will see, I did file a ticket on github.
opened 12:13AM - 19 Oct 25 UTC
needs-author-feedback
### Windows Version
Microsoft Windows [Version 10.0.19045.6456]
### WSL Versio… n
WSL version: 2.6.1.0
### Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
### Kernel Version
Kernel version: 6.6.87.2-1
### Distro Version
Ubuntu-24.04
### Other Software
Docker Desktop Version 4.48.0 (207573)
### Repro Steps
Unfortunately I am unsure of what caused the issue, but I can walk you through the steps I did before I had an issue.
I had ran out of space on my system drive. Looked up how to relocate my WSL image to a different hard drive. Followed the steps from [here](https://learn.microsoft.com/en-us/windows/wsl/faq#how-can-i-move-my-wsl-distribution-to-a-different-drive-or-location-).
I exported both my Ubuntu and Docker Desktop distros to a separate hard drive. Deregistered both distros then imported both with the `--import-in-place` command. Booted my Docker Desktop back up and tried to access my containers via my configured DNS setting. Determined my apps would not resolve. Then proceeded to testing all possible ways to access the apps `localhost:<app-port>`, `127.0.0.1:<app-port>`, and `<my host ip>:<app-port>`. The **_only_** option that worked was `localhost:<app-port>`.
Note: I later discovered my Docker Desktop ext4.vhdx image disappeared after I restarted Docker Desktop because this is **not** the correct way to move the image. There is an setting under `Settings > Resources > Advanced > Disk image location`.
### Expected Behavior
I should be able to (and used to be able to) access my Docker containers via my host LAN ip address (for example 192.168.1.2) and the local host ip address (127.0.0.1).
### Actual Behavior
Accessing my containers via LAN ip and/or the localhost ip gives me an `ERR_CONNECTION_TIMED_OUT`.
### Diagnostic Logs
I am sending logs via email. Note I saw some errors while trying to produce the log file so it may be incomplete.
1 Like
.