Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blank screen with microsoft-edge image #376

Open
amenolo opened this issue Mar 16, 2024 · 8 comments
Open

Blank screen with microsoft-edge image #376

amenolo opened this issue Mar 16, 2024 · 8 comments
Labels
not our bug Bug is inside used dependency / library

Comments

@amenolo
Copy link

amenolo commented Mar 16, 2024

In following scenario

  • docker running on debian 12 VM (tested under debian 12 LXC too, both unpriviledge and priviledge with default config) behind properly set NAT and reverse proxy (NPM)
  • microsoft-edge image started via default docker-compose file
  • Firefox and Edge as client browser (with disabled add-ons) under GNOME and Windows

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!

@m1k1o
Copy link
Owner

m1k1o commented Mar 16, 2024

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.

@amenolo
Copy link
Author

amenolo commented Mar 17, 2024

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.

@m1k1o
Copy link
Owner

m1k1o commented Mar 23, 2024

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.

@m1k1o m1k1o added the not our bug Bug is inside used dependency / library label Mar 23, 2024
@amenolo
Copy link
Author

amenolo commented Mar 24, 2024

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.

@m1k1o
Copy link
Owner

m1k1o commented Mar 24, 2024

Do they have it open sourced? Or could we take a look on what they do differently?

@amenolo
Copy link
Author

amenolo commented Mar 24, 2024

@ehfd
Copy link

ehfd commented Mar 24, 2024

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'"

@ehfd
Copy link

ehfd commented Mar 24, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not our bug Bug is inside used dependency / library
Projects
None yet
Development

No branches or pull requests

3 participants