[GH-ISSUE #677] ERRO[0094] error waiting for container: #511

New issue

Open

opened 2026-02-27 23:00:52 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 23:00:52 +03:00

Owner

Originally created by @freshlesh3 on GitHub (Jul 10, 2023).
Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/677

I run this command:

docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
-e GENERATE_UNIQUE=true
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist'
sickcodes/docker-osx:monterey

The image is pulled and then I get this error:
Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:50922 -> 0.0.0.0:0: listen tcp 0.0.0.0:50922: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

I am using windows 11. I have tried using other ports, running docker with sudo. I've reinstalled Docker, and tried resetting to factory to reset my network configuration but nothing seems to work.

Originally created by @freshlesh3 on GitHub (Jul 10, 2023). Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/677 I run this command: docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e GENERATE_UNIQUE=true \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ sickcodes/docker-osx:monterey The image is pulled and then I get this error: Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:50922 -> 0.0.0.0:0: listen tcp 0.0.0.0:50922: bind: An attempt was made to access a socket in a way forbidden by its access permissions. I am using windows 11. I have tried using other ports, running docker with sudo. I've reinstalled Docker, and tried resetting to factory to reset my network configuration but nothing seems to work.

kerem commented

2026-02-27 23:00:53 +03:00

Author

Owner

@vitoras commented on GitHub (Oct 28, 2023):

Hi, have you found a solution? I'm facing the same issue.

@vitoras commented on GitHub (Oct 28, 2023): Hi, have you found a solution? I'm facing the same issue.

kerem commented

2026-02-27 23:00:53 +03:00

Author

Owner

@smshafa commented on GitHub (Nov 22, 2023):

First of all, quit your Docker Desktop, and then
Run CMD or PowerShell as administrator:

net stop winnat
net start winnat

@smshafa commented on GitHub (Nov 22, 2023): First of all, quit your Docker Desktop, and then Run CMD or PowerShell as administrator: `net stop winnat` `net start winnat`

kerem commented

2026-02-27 23:00:53 +03:00

Author

Owner

@eabugda commented on GitHub (Nov 25, 2023):

This worked for me, thanks!

@eabugda commented on GitHub (Nov 25, 2023): This worked for me, thanks!

kerem commented

2026-02-27 23:00:53 +03:00

Author

Owner

@jostickquielciat commented on GitHub (Apr 28, 2024):

Works for me too

@jostickquielciat commented on GitHub (Apr 28, 2024): Works for me too

kerem commented

2026-02-27 23:00:53 +03:00

Author

Owner

@xccElephant commented on GitHub (Nov 10, 2024):

First of all, quit your Docker Desktop, and then Run CMD or PowerShell as administrator:

net stop winnat net start winnat

Thanks, this works for me!

@xccElephant commented on GitHub (Nov 10, 2024): > First of all, quit your Docker Desktop, and then Run CMD or PowerShell as administrator: > > `net stop winnat` `net start winnat` Thanks, this works for me!