Ports are not available: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

[jongeuni]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics

Information

• Windows Version: Window 10 Home
• Docker Desktop Version: 4.4.4
• WSL2 or Hyper-V backend?: WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Actual behavior

I executed the container. The port was 5432.

Expected behavior

The container should be running, and the 5432 port should have been opened.

Issues

The container was not executed and a port error appeared. When I looked it up, it was an error that appeared when the port was already present. However, t when I checked cmd, there was no 5432 on the running port. (port was not running.)

Error invoking remote method 'docker-start-container': Error: (HTTP code 500) server error - Ports are not available: listen tcp 0.0.0.0:5432: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

Error invoking remote method 'docker-start-container'
: Error: (HTTP code 500) server error - Ports are not available: listen tcp 0.0.0.0:5432: bind
: An attempt was made to access a socket in a way forbidden by its access permissions.

---

I solved this problem. But I saw people struggling with this problem. Borrowed 'Issues' to help them more faster.

[jongeuni]

Hello. In order to solve this problem, we need to know the cause.

First, make sure that the port is running. (If port running, close the port and run the action again.) If the port is not running, let's go find out the cause together. Go Go.

Enter netsh interface ipv4 show excludedportrange protocol=tcp in cmd. (or powershell... etc.)

Look at the cmd.(or powershell.) It is not available from the start port to the end port. This changes every time the computer is turned off and on.

So I solved it by restarting the computer and re-logging into the docker desktop.

---

I haven't tried this myself, but I'm sure it's a more effective and efficient way then above.

1. Before executing the docker, run the powershell as an administrator.
2. netsh interface ipv4 show excludedportrange protocol=tcp You can see that the range of port that Windows System reserved for the first time are very small.
3. At this point, use the following instructions to reserve the port you want to use.
   netsh int ipv4 add excludedportrange protocol=tcp startport=5432 numberofports=1 store=persistent
   This means that I will use one port from 5432.
4. If you make a reservation like this and check it with the command netsh interface ipv4 show extended portrange protocol=tcp, you can see that the desired port is reserved with a (*) mark on the reserved port.

---

Please understand even if the English sentence is weird. 😥

[docker-robott]

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

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked