docker-for-win:permission denied, then silent crash

[peter17ji]

win10 19041.208, docker desktop 2.2.0.5 stable, wsl2 ubuntu 18.04, vcxsrv-64.1.20.8.1
https://pastebin.com/eDG9hBjD

[peter17ji]

Installed and reinstalled via zip distribution, ran x11docker/check and crashed.
https://pastebin.com/kc0daKyj

[peter17ji]

[Edited] x11docker.log at pastebin.com: https://pastebin.com/vaK7S0dx

[mviereck]

Thank you for the report!

The core error message is:

 /usr/bin/x11docker: line 8302: /usr/local/bin/runx: Permission denied

Somehow runx failed although it is installed.
Could you please try to run runx on its own and show me the output?
E.g. install xterm in WSL2 and try:

runx --verbose -- xterm

(Edit: For long outputs please use www.pastebin.com. It is easier to read. I've edited your previous posts accordingly.)

[eine]

That sounds to me as a chmod +x runx issue... Maybe installing from zip does not preserve file permissions?

[peter17ji]

Thank you for the report!

The core error message is:

 /usr/bin/x11docker: line 8302: /usr/local/bin/runx: Permission denied

Somehow runx failed although it is installed.
Could you please try to run runx on its own and show me the output?
E.g. install xterm in WSL2 and try:

runx --verbose -- xterm

(Edit: For long outputs please use www.pastebin.com. It is easier to read. I've edited your previous posts accordingly.)

Surprisingly nothing happens when I run runx. No error, no info, even no version output.

C:\Users\peter>bash
peter@DESKTOP-56G7F0B:/mnt/c/Users/peter$ docker --version
Docker version 19.03.8, build afacb8b7f0
peter@DESKTOP-56G7F0B:/mnt/c/Users/peter$ uname -a
Linux DESKTOP-56G7F0B 4.19.84-microsoft-standard #1 SMP Wed Nov 13 11:44:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
peter@DESKTOP-56G7F0B:/mnt/c/Users/peter$ x11docker --version
6.6.1
peter@DESKTOP-56G7F0B:/mnt/c/Users/peter$ runx --verbose -- xterm
peter@DESKTOP-56G7F0B:/mnt/c/Users/peter$ runx --version
peter@DESKTOP-56G7F0B:/mnt/c/Users/peter$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

[peter17ji]

Has made sure xrun binary is in /usr/local/bin, but still doesn't work.
https://pastebin.com/S1wiiegr

[peter17ji]

Binary .zip downloaded from github using Firefox windows desktop version, then unzipped into ~/ using UnZip 6.00 ubuntu apt distribution. For Mainland China's permanent network issues, direct install via curl or wget is not available and creates SSL cert invalid error.

[eine]

Can you run it by providing the absolute path explicitly? /usr/local/bin/runx -h.

[mviereck]

Your checks on pastebin shows that the file /usr/local/bin/runx is empty, cat shows no output:

peter@DESKTOP-56G7F0B:~$ cat /usr/local/bin/runx
peter@DESKTOP-56G7F0B:~$ ls /usr/local/bin ||grep runx
kubectl  runx

Something has gone wrong during download or unzip.
I've downloaded https://github.com/mviereck/runx/archive/master.zip. The extracted folder shows:

$ ls -l runx-master
insgesamt 36
-rw-r--r-- 1 lauscher lauscher  1080 Mär  5 15:50 LICENSE
-rw-r--r-- 1 lauscher lauscher  7674 Mär  5 15:50 README.md
-rwxr-xr-x 1 lauscher lauscher 23984 Mär  5 15:50 runx

Please download and unzip again and check that you get the same output as this one, especially the same file size 23984 and file permissions -rwxr-xr-x for runx.

[peter17ji]

Still doesn't work after manually copying runx over to /usr/local/bin, but seems to be related to #108 .
https://pastebin.com/J6UWBVK0
Solely using runx produces same error. Disabling all firewalls doesn't help at all.

[peter17ji]

Seems to be about WSL2 vEthernet implementation. microsoft/WSL#4139
Will try solutions mentioned there.

[mviereck]

The log shows a different issue. runx cannot find VcXsrv or XWin:

�[41mrunx ERROR:�[0m No X server found.
  Please either install X server VcXsrv:
      https://sourceforge.net/projects/vcxsrv
  or install Cygwin with packages xinit and xauth to provide XWin:
      https://www.cygwin.com/

• Please check your VcXsrv installation.
• Please try to get runx to work before trying x11docker.
  This command has to work before you can try to run x11docker:

runx --verbose -- xterm

[mviereck]

Could you show me the output of runx --verbose -- xterm, please?

[mviereck]

Closing due to low activity.