Aterfax / DCS-World-Dedicated-Server-Docker

Modular DCS World Dedicated Server docker.
GNU General Public License v3.0
30 stars 6 forks source link

Unable to open the web browser within the KasmVNC Client #36

Open hannibalpostumus opened 7 months ago

hannibalpostumus commented 7 months ago

This is an issue I encountered using Afterfax's previous solution that was posted on Reddit and it has made a comeback. It's probably localised to the way I setup my system but it is recurring though probably results from my ignorance of Docker intricacies.

I use a bind mount on my server:

volumes:
      - /mnt/storage/dcs_server/:/config/

Using standard PUID and GUID of 1000 in the Docker compose, after a while of operating, I start experiencing a strange bug - the web browser refuses to open. The docker logs aren't particularly helpful here but they do hint at the possibility of a permissions issue - I attach the relevant parts below.

I've tried re-deploying the container to no avail and as an experiment, even changed the folder permissions recursively on the host machine to 777 just to see if this would work, but still nothing. I'm currently unable to access the WebGUI of the server and nothing short of rebinding to a new location (along with copying or re-downloading the DCS files) will fix the issue.

I'm posting here as an open issue in case anyone else has had this problem or, as is more likely, I'm doing something stupid on my end, in which case, excuse the ignorance!

GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1000
───────────────────────────────────────
s6-rc-oneshot-run: fatal: unable to exec /etc/s6-overlay/s6-rc.d/init-getlatest-dcs-installer-oneshot/run: Permission denied
s6-rc: warning: unable to start service init-getlatest-dcs-installer-oneshot: command exited 126
[custom-init] No custom files found, skipping...
s6-rc-oneshot-run: fatal: unable to exec /etc/s6-overlay/s6-rc.d/init-winepreqs-oneshot/run: Permission denied
s6-rc-oneshot-run: fatal: unable to exec /etc/s6-overlay/s6-rc.d/init-desktop-setup-oneshot/run: Permission denied
s6-rc: warning: unable to start service init-winepreqs-oneshot: command exited 126
s6-rc: warning: unable to start service init-desktop-setup-oneshot: command exited 126
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Xvnc KasmVNC 1.2.0 - built Dec  9 2023 18:40:46
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation
 2023-12-16 12:26:45,579 [INFO] websocket 0: got client connection from 127.0.0.1
 2023-12-16 12:26:45,604 [PRIO] Connections: accepted: @79.185.30.221_1702726005.580413::websocket
Aterfax commented 7 months ago

That unable to exec part is looking more likely to be Github / Git / Windows stomping POSIX permissions during the Git commit / docker build. I shall have a look in a bit.

Aterfax commented 7 months ago

Will merge the permissions fix shortly. But that won't resolve issues with Chromium not launching. The browser issue is related to:

Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
[4296:4296:1216/120527.737986:FATAL:zygote_host_impl_linux.cc(201)] Check failed: . : Operation not permitted (1)
[1216/120527.742965:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
[1216/120527.743111:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
[1216/120527.743287:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[1216/120527.743312:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Trace/breakpoint trap

Tested without:

    security_opt:
      - seccomp:unconfined 

Which is likely going to be something fixed or a mitigation provided by the upstream Webtop docker.

Aterfax commented 7 months ago

Perms fix for any of those service start issues now available from: https://github.com/Aterfax/DCS-World-Dedicated-Server-Docker/pull/37 which will be rebuilding the image as we speak.

Aterfax commented 7 months ago

I've referenced this issue on the webtop Git repo, in the meantime you can easily mitigate by either: