You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running docker compose up on Windows with WSL2/Hyper-V, the container fails to start because ports 8085 and 11451 fall within Windows Hyper-V dynamically excluded port ranges.
CLI Type
NA
Model Name
NA
LLM Client
NA
Request Information
netsh interface ipv4 show excludedportrange protocol=tcp
Expected behavior
docker compose up -d runs correctly
Screenshots
NA
OS Type
OS: Windows 11
Latest
Additional context
The recent windows update appears to now reserve new ports that prevents docker compose from running as it currently is on WSL2. I must now edit the file in order to run it.
I modified to the following port list to get around the Hyper-V reserved port issue.
This discussion was converted from issue #387 on December 02, 2025 04:01.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When running docker compose up on Windows with WSL2/Hyper-V, the container fails to start because ports 8085 and 11451 fall within Windows Hyper-V dynamically excluded port ranges.
CLI Type
NA
Model Name
NA
LLM Client
NA
Request Information
netsh interface ipv4 show excludedportrange protocol=tcp
Expected behavior
docker compose up -d runs correctly
Screenshots
NA
OS Type
Additional context
The recent windows update appears to now reserve new ports that prevents docker compose from running as it currently is on WSL2. I must now edit the file in order to run it.
I modified to the following port list to get around the Hyper-V reserved port issue.
Beta Was this translation helpful? Give feedback.
All reactions