Open walterzilla opened 6 months ago
If you say other images are working flawlessly (speecifically chrome) then it might be something specific to edge why its not starting. Do you see any error logs from edge? You should see them in container logs, or here /var/log/neko/microsoft-edge.log
.
If you say other images are working flawlessly (speecifically chrome)
Correct!
Do you see any error logs from edge?
Several errors here and there for sure but I guess some are physiological and in any case no one fatal, actually I'm unable to identify any discriminating ones so I'm going to attach logs for your consideration.
ungoogled-chromium_container_start.log microsoft-edge_container_start.log ungoogled-chromium_client_connection.log microsoft-edge_client_connection.log
BTW I happen to notice that microsoft-edge image behavior (i.e. local+remote cursor only) exactly matches other chrome/chromium-based image behavior with SYS_ADMIN option being removed, maybe could help further addressing the issue...thanks!
UPDATE
Out of curiosity I just tried to install and use same docker image on a commercial VPS with public IPv4 (therefore no NAT and no potentially networking setting issue) resulting in the same behavior.
I was able to test this on my computer and yes, it seems to be some issue with the edge itself. It is not starting, probably some change on their side, it either needs more permissions or some specific arguments to run in docker.
Maybe could help knowing that e.g. edge docker image from Kasm Workspaces works flawless? Anyway I'm not a code guy so I'm not that useful here...still I'm open to do further tests, thanks for your feedback.
Do they have it open sourced? Or could we take a look on what they do differently?
Do they have it open sourced?
https://github.com/kasmtech/workspaces-images/blob/develop/dockerfile-kasm-edge
https://github.com/kasmtech/workspaces-images/blob/develop/src/ubuntu/install/edge/install_edge.sh
They have a very long list of arguments. I'd say to put in --no-sandbox --ignore-gpu-blocklist
initially and try again.
CHROME_ARGS="--password-store=basic --no-sandbox --ignore-gpu-blocklist --user-data-dir --no-first-run --simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT'"
Needs testing. I'd say it's --no-sandbox
missing in the non-NVIDIA Neko container, but not sure. I'll help out with the container work, but the container overhaul needs to be done in conjunction with #371.
In following scenario
I get the mouse cursor only. Issue doesn't show up in any other use case (i.e. the other images are working flawless).
What am I missing? Any idea? Thanks!