Closed garex closed 7 years ago
@garex Thanks for using this image! Have you checked whether wine
is running or not? I experienced this error as well, but it did not seem to have any impact. See here.
Please also see this hint from x11docker (commented on the image description on hub.docker.com):
To X error ... Bad Value: your apps in docker try to access shared memory from X (X extension MIT-SHM). You can either allow access with docker run option --ipc=host, but this breaks container isolation. Otherwise, you should run your X server with MIT-SHM disabled ( X option -extension MIT-SHM). I solved this problem with x11docker, running a second X server without MIT-SHM (and without the need of VNC, by the way)
Haven't tried it, but might work as well.
If you have further questions please feel free to open a new issue.
A possible fix mentioned here https://github.com/osrf/docker_images/issues/21#issuecomment-239334515
wine wineboot --init
I got: