-
Notifications
You must be signed in to change notification settings - Fork 379
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
docker-for-win: Cannot establish any listening sockets - Make sure an X server isn't already running #155
Comments
Thanks for reporting! It seems that x11docker somehow does not recognice X display numbers that are already in use. I successfully runs the first X server on display I'll have a look why the display number check fails. Meanwhile it should work if you manually specify a different display number with |
It works. I'm using this now to run the checks. |
Ok, this one is fixed in latest commit. I did some test runs in a Windows VM, |
I can confirm that it works now. |
I think I'm having this problem in Cygwin: Note that there is no other Xwin server running, but there is an VcXsrv running at I can work around this issue with |
I did a test run yet with this setup, and it works. |
x11docker is not 'installed', I clone/pull the git repo and execute the script from there. Note that the command I used is |
I cannot reproduce the issue, works ok here. |
I'm using the latest |
I'll look into that, but it is quite unlikely. If started within Cygwin, x11docker checks
Could you please try an older version? |
I tried with |
Thank you.
Of interest is
Can you show me In MSYS2 this probably fails, but this should work:
Maybe you can also run a check with |
This was it. Moreover, the authorization issue commented in #145 does not apply to cygwin (either with xwin or vcxsrv). It is still present with MSYS, tho. |
Oh, ok. I thought it would be part of the
Does |
Great!
Yes, it does exist. The following executables are available in EDIT
|
I tried to run the checks #145 after updating to the latest master, and I found the following error:
/path/to/x11docker/x11docker --user=0 -i -- -v /$(pwd)://src -- aptman/dbhi:bionic bash
. Both the container and the X server are still running and working as expected../x11docker --hostdisplay --gpu x11docker/check
. I get the following error:VCXSrv.100.log
x11docker.log
Then, I closed all the containers and X servers, and tried again. The interface of
x11docker/check
is now properly shown.Last, I started the
aptman/dbhi
container again, and tried to executex11docker/check
after it. It fails again.So, I'd say that some of the latest changes have broken the possibility to start multiple vcxsrv instances.
The text was updated successfully, but these errors were encountered: