No suitable graphics card found

[webanck]

No suitable graphics card found

[webanck]

Ok, one of the first solutions I get when looking for this error on the web would be to add the user to the video group.
Could you edit the Dockerfile at the beginning after the wine user creation like this?

RUN useradd -u 1001 -d /home/wine -m -s /bin/bash wine
RUN useradd -G video wine

And try to rebuild the image and relaunch the container?
By the way, it it's still not working, could you provide details on your linux distribution?

[juicetin]

Hmm it gets stuck at RUN useradd -G video wine when I add that, telling me 'useradd: user 'wine' already exists'. EDIT: currently testing using 'RUN usermod -a -G video wine' instead.
EDIT: No luck unfortunately.

In any case, I'm running Linux version 4.0.7-2-ARCH - let me know what extra information you want regarding my setup should you need it

[webanck]

Ok, maybe it tries to create a new user with the former command, try this one instead?

RUN usermod -a -G video wine

EDIT: yeah, exactly what I was suggesting...
EDIT: could you try with the initial version of the file and paste the building log?

[juicetin]

Sure thing - I'll edit this post with a pastebin link once I've run it again.

Huh - I got a lot of errors with resolving URLs, which was kinda strange. I might try redo all of it from scratch (wipe and re-pull the repository), but here it is for now - https://gist.github.com/jyting/8a038e1ffad092b03160

Actually, my machine has an integrated graphics card - do I need to tweak much in builder.sh?

It may be of note, but I tested with some other small games and they ran without issue - it was terraria specifically that had problems.

Wine seems to need a password which I don't recall ever setting when trying to run 'sudo usermod -a -G video wine' from within the docker instance, but no wine user exists when trying to run that from my linux machine - perhaps it would work if I were able to run the command?

[webanck]

I will look further later but be aware that you can't sudo once inside the container instance.
It's the Docker way to prevent exploits from inside root.
That's why the command needs to be added to the building process when the user is still superuser.

About the URLs errors, it happens sometimes, retrying should eventually do the trick.

EDIT: I will run some tests on my own laptop but try tweaking the builder.sh script replacing the Intel package by xserver-xorg-video-intel.
EDIT: in fact I tried to build the image on my laptop with an integrated graphic chipset but I allways got an error about the sha1sum of the corefonts winetricks download. We might have to wait for the font source or winetricks to be updated...

[juicetin]

Thanks for the follow up - I wasn't able to get past the issues I mentioned previously either. In the meantime, I just dug up an old laptop (core duo, 2gb RAM!) to play it on until it's released for Linux, which shouldn't be more than few weeks from now anyway.