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
Basic video test fails #44
Comments
Hi @lostfictions docker run -it \
--rm \
--env="DISPLAY" \
--volume="${XAUTHORITY:-${HOME}/.Xauthority}:/root/.Xauthority:ro" \
--volume="/tmp/.X11-unix:/tmp/.X11-unix:ro" \
--volume="/etc/localtime:/etc/localtime:ro" \
--volume="winehome:/home/wineuser" \
--hostname="winecellar" \
--name="wine" \
scottyhardy/docker-wine wine notepad |
thanks for the quick reply! $XAUTHORITY is defined for me and points to the right place -- i tried this just in case and it doesn't seem to make a difference. |
Ok, I've got an Ubuntu 16.04 VM and can confirm I get the same errors. I've gone back to an older version of my scripts and found that running with this will work: docker run -it \
--rm \
--env="DISPLAY" \
--volume="winehome:/home/wineuser" \
--name="wine" \
--network="host" \
scottyhardy/docker-wine wine notepad It's hardly ideal though as I'd been trying to move away from insecure settings like |
Aha! I've found the problem - apparently .Xauthority cookie is dependent on the hostname matching for some OSes. So, this will work: docker run -it \
--rm \
--env="DISPLAY" \
--volume="${XAUTHORITY:-${HOME}/.Xauthority}:/root/.Xauthority:ro" \
--volume="/tmp/.X11-unix:/tmp/.X11-unix" \
--volume="winehome:/home/wineuser" \
--hostname="$(hostname)" \
--name="wine" \
scottyhardy/docker-wine wine notepad I'll add this to the dev branch soon and do a release with the update soon 😄 |
amazing! thanks so much for all the work you've put into this :) |
Same issue for me. And @scottyhardy 's latest reply solved the problem. Thanks very much for your nice work! |
Just for your information, this is my argument list:
If someone is using an Nvidia driver and PulseAudio in Ubuntu 16.04, probably he needs some more arguments to make complex games work. Key tricks:
I am not sure whether these arguments are essential for other OSes. But when I tried to run WinKawaks in the container, I have to setup everything like the above. Hopefully this will give inspirations when others face similar issues. Cheers! |
I ran into this issue just now, and the fix in #44 (comment) worked for me. @scottyhardy I see the fix was added to aabcfa1, any chance we could get that release now? @gluckzhang I'm getting a similar GL error:
so I was trying to follow your solution, without success yet. Do you remember how you found the |
Hi @501st-alpha1 , sorry but I forget how I find the exact path to
|
@501st-alpha1 Yep, I've decided to give this little project some more attention so I'll get onto releasing this fix very soon |
Now fixed in release 2.1.0 |
hey there, i can't seem to get the image or script to work. it pulls the image fine, and running the script without arguments gives a bash shell as expected, but running the suggested troubleshooting command fails:
okay, not sure what any of that means -- let's check
$DISPLAY
:seems fine to me?
as a test, let's delete the
winehome
volume just in case:that seems worse, not better!
this is on ubuntu 16.04. here's some additional output in case it helps diagnose this:
The text was updated successfully, but these errors were encountered: