docker-for-win: firewall settings / no X window appears

[eine]

Coming from #87 (comment)

I tried the following:

• Allow VcXsrv windows xserver in Private and Public networks.
• Start vcxsrv with xlaunch: Multiple windows, Display number 0, Start no client, Clipboard, Disable access control.
• winpty docker run -it -e DISPLAY=10.0.75.1:0.0 alpine_term xterm works.
• Stop vcxsrv.
• Allow VcXsrv in Private networks only.
• Start vxcsrv again with xlaunch.
• winpty docker run -it -e DISPLAY=10.0.75.1:0.0 alpine_term xterm does not work.

However, x11docker does not work with any of them.

Last, I disabled the firewall everywhere (Domain network, Private network and Public network). Now x11docker works.

So, it is strange that this problem did not happen earlier. Although it might sound strange, I think that this might have something to do with changing from wireless to ethernet recently. I did change nothing more these last days.

Will have to investige further.

[mviereck]

Allow VcXsrv windows xserver in Private and Public networks.
Start vcxsrv with xlaunch: Multiple windows, Display number 0, Start no client, Clipboard, Disable access control.
winpty docker run -it -e DISPLAY=10.0.75.1:0.0 alpine_term xterm works.

I do not see why x11docker would not work where any sort of docker run -it -e DISPLAY works.
For more similarity you could add --no-auth --clipboard --gpu and even --display=0. But I would not expect a difference due to this settings.

I think that this might have something to do with changing from wireless to ethernet recently. I did change nothing more these last days.

Maybe a regular Windows update that changed something, too?

[eine]

Well, I enabled the firewall again (Domain network, Private network and Public network), and it now works. vcxsrv must be enabled for private and public networks, but now x11docker behaves as well as docker run -it -e DISPLAY.

Maybe a regular Windows update that changed something, too?

Might be.

I'm closing this, because I don't know what did break or fix it.

[mviereck]

Thank you for reporting and investigation!
I have added a note about this in README.md and a message in x11docker.
I will keep this ticket open for those who might stumble over it, too.

[eine]

Today I found the same issue when using --xwin in Cygwin (#120). I had to set the firewall to allow xwin in both public and private networks.

[mviereck]

Also in wiki, closing.
https://github.com/mviereck/x11docker/wiki/x11docker-on-MS-Windows