Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

winsock error: cannot create listening socket #154

Open
moth1995 opened this issue Nov 6, 2022 · 2 comments
Open

winsock error: cannot create listening socket #154

moth1995 opened this issue Nov 6, 2022 · 2 comments

Comments

@moth1995
Copy link

moth1995 commented Nov 6, 2022

hi! first of all thanks for this amazing docker image, really nice
i'm trying to run a game server that only has support for windows after the installation the application runs correctly, altho it seems that the ports are close, but on my host machine they're open and i expose the ports, if i close the application then it throws the error cannot create listening socket, i have to kill the container and start a new one, but i never manage to make it work, before testing this on wine i run test over my windows machine (win10) and works correctly

this is how i run the container

docker run -d -it --rm --hostname="$(hostname)" --env="RDP_SERVER=yes" --publish="3389:3389/tcp" --publish="9250:9250/tcp" scottyhardy/docker-wine /bin/bash

after this i do rdp into the container and install with the windows wizard the app and just configure the basic stuff

imagen

the port is 9250 tcp

iptables -nL | grep 9250
ACCEPT tcp -- 0.0.0.0/0 172.17.0.3 tcp dpt:9250

I believe there's something related to the communication between the docker and linux host machine there's anything i can provide apart from what im actually sharing? im pretty new to wine itself after the first try seems to be pretty easy

thanks for the future help

EDIT: if you do need me to upload the app so you test i can do it

@Lexian-droid
Copy link

I tried your command, as I'm trying to figure out how to publish a port, and I'm having an issue where all the data is deleted when the container is stopped. So, if I had to guess, I think it's because you didn't map a volume of some sort.

@Lexian-droid
Copy link

Try something like this:

docker run --name docker-wine -d -it -p 3389:3389 -v winehome:/home/wineuser -e RDP_SERVER=yes --rm scottyhardy/docker-wine /bin/bash

Maybe that will work, I'm not 100% sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants