Docker debugging opening not specified ports (57000 and 571000)

Hi, 

After scratching my head for far too many days I can't find any answer why is Rider opening ports 57000 and 57100 when debugging dot net core project in docker.

I have not specified those ports anywhere and can't find any place in settings to specify those. 

The problem is I have 2 projects that need to be debugged at the same time and when I'm trying to run them, on the second project I'm getting an error that the port is already in use.

Is there any way I can change those ports?

1
4 comments
Avatar
Permanently deleted user

Today I got the same problem, I have only add port bind for port 5000, but when I navigate to docker, selected container -> Port Bindings tab I see that ports 5000, 57100 and 57000 are exposed

0

Was there ever a solution to this? I'm running into the same issue now

0

I am having the same issue anyone found a solution?

0

Hey Glen Doci,

In the current moment Rider should not use the same ports for the debug with Docker. At the moment new port is picked up each time. 

Thus, could you please clarify exact steps to reproduce? What error do you see? Can you please reproduce the issue and collect a full log bundle? You may want to upload logs to our storage https://uploads.jetbrains.com/ or create a new issue on our YouTrack and attach logs there.

Thank you in advance! Looking forward to hearing from you soon.

0

Please sign in to leave a comment.