Open kiview opened 3 years ago
This fix would make me soooo happy. The ryuk issue hits me daily...
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
/remove-lifecycle stale
I hit this a ton too, would love a fix. Definitely related to #3171
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
/lifecycle frozen
Froze it because it is still an issue and it can make usage very difficult in normal workflows.
I encountered the same problem / could reproduce the error. By enabling Hyper-V in the Windows-Features, I was able to solve the problem for me.
@LarsSchlieper Enabling Hyper-V on Windows 11 Pro, but still using the WSL backend in Docker?
@kiview Enabling Hyper-V on Windows 10 Pro (not 11), but still using the WSL backend in Docker. Yes.
Actual behavior
Using the
--publish-all
flag will start at a certain high port and subsequently increment the mapped port number with each consecutive mapped port. However, following this process might lead to mapping ports that are part of the excluded port range of Windows network config.Running
netsh interface ipv4 show excludedportrange protocol=tcp
in Powershell resulted in the following excluded port ranges on my machine (with nothing configure manually):After a Docker restart, using the
--publish-all
flag will deterministically start at port 49153. This means, after mapping 25 ports after Docker restart, the excluded port range of 49177 is reached, and subsequently mapped ports using--publish-all
won't be reachable anymore (although the container starts successfully).Expected behavior
It should be possible to access the mapped ports if ports are published using the
--publish-all
flag.Information
Steps to reproduce the behavior
From within WSL2, create a number of containers with
--publish-all
until the mapped ports end up in the excluded range:The range might be system-dependent, but for me, creating ~30 containers after Docker restart is enough to run into the excluded range.
Afterward, accessing the containers with ports mapped in the excluded range is not possible, e.g.: