Closed st3rven closed 3 months ago
Hello
Can you check if the virtual desktop process are running ?
Run ps -faux
inside your container to check.
If there is none, try to run desktop-start
and screenshot the output to see if there is any error
Thank you
Hi @Dramelac,
the process is not running, and when I tried to execute the mentioned command I receive the following error message:
assertion failed [rem_idx != -1]: Unable to find existing allocation for shared memory segment to unmap (VMAllocationTracker.cpp:745 remove_shared_mem)
Hi all
Same issue with this configuration :
Host OS: Fedora
Exegol version: 4.3.4
Image: full - v.3.1.4
Firefox: 128.0
Test the same command :
Can't access I try to recreate workspace.... Nothing
Thank's for your help
Unable to find existing allocation for shared memory segment to unmap
Hello @st3rven I have found this post with the same kind of error: https://forums.docker.com/t/unable-to-find-existing-allocation-for-shared-memory-segment-to-unmap/139868 You can try to fix it by increasing the virtual disk limit in docker desktop
Hello @cdrmx we've heard of a bug with fedora and the desktop feature, we're investigating.
Hi @Dramelac The error persists even after updating to 240 GB. My configuration.
Hi @Dramelac The error persists even after updating to 240 GB. My configuration.
We were unfortunately unable to reproduce. I'm not sure where the error is, either from vnc service or from docker desktop. Maybe try to use orbstack instead of docker desktop to see if the bug persist.
I installed OrbStack and migrated the container (without creating a new one), and I donβt know what kind of black magic it does, but it works! So, the most logical conclusion is that the issue lies with Docker Desktop. I guess itβs just another one of lifeβs mysteries.
Yeah docker desktop have a lot of weird bug ^^' Enjoy your desktop ! I'm closing this issue because it was related to a desktop bug on Docker Desktop but, (@cdrmx) regarding fedora, a patch will be deploy with the next nightly image !
Describe the bug
Hi! Iβm just starting to use Exegol and Iβm having trouble using the remote desktop option. The port appears to be listening on my host machine, but I canβt access the service.
Environment
Evidence:
Container start
Curl from host
Host: port is listening
Container: Any service is listening
Steps To Reproduce
No response
Exegol Wrapper Version
Host OS
MacOS
Configuration of the concerned container
No response
Execution logs in debug mode
Exception
No response
Anything else?
No response