Open hannibalpostumus opened 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.
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.
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.
I've referenced this issue on the webtop Git repo, in the meantime you can easily mitigate by either:
sudo apk add firefox
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:
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!