[REL] Linux dedicated server with docker and wine
-
Delenda did a quick test and could confirm my observations: Everything is working fine
Regards
Blacksheep -
Awesome work, folks!
Uwe
-
Step 75 is incorrect.
Also the amount of steps is too high, consider configuring the dedicated system from a batch file or making your own system image.
-
Hi Blacksheep,
Been having a go at the image you posted to the Docker hub. Have some feedback for you.
As sthalik mentioned, in your steps, number 75 has a typo:
set vblank_mode=0docke ```should be
set vblank_mode=0
In order to get a dummy sound device in, you'll need to use modprobe which requires the container to run in a privileged mode and needs access to /lib/modules on the host. The following args when using 'docker run' will assist:
–privileged
–cap-add=ALL
-v /lib/modules:/lib/modulesmodprobe will then work. I had issues with this as OVH doesn't supply the stock kernel for Ubuntu, so I had to remove OVH's one and put the Ubuntu one back before I could load kernel modules. I was hoping to use jackd instead of replacing the kernel but this seemed easier in the end! Was running out of space in the container when adding theatres, so I added a volume that resides on the host:
-v <somewhere_on_host>:/home/blacksheep/.PlayOnLinux/</somewhere_on_host>
I've stopped xcreensaver too as that was becoming a pain :) Still haven't got the nogpu DLLs working - only the last arg in the 'Command to exec before running the program' is showing in the top left when the launcher starts, not sure if that's relevant? Thanks for all your work so far, appreciate it! Cheers, Del
-
Hi Del,
thank you for the feedback.
All I can say is that I didn’t needed the –privileged and --cap-add stuff. My way was to ensure that alsa is installed on the host and the snd-dummy driver is being loded. In the docker container I loaded then the snd-dummy module too. I didn’t understood yet why this was necessary but this finally did the trick.
Did you try to run the IVC server from the launcher? If this is not running we can assume that this is a generic wine issue. If it runs, we may focus on the nogpu stuff.
Would be great if you can provide the following:
- Screenies from the configuration (all tabs):
Start PlayOnLinux -> Select Launcher -> Configure Button on the right top - Run BMS in Debug mode:
In PlayOnLinux -> Select Launcher -> Klick on Debug in the left pane
Post the log when BMS crashed.
Actually I am quite busy, so my answer times will be not that quick.
Regards
Blacksheep - Screenies from the configuration (all tabs):
-
No worries about slow answers dude, appreciate the assist.
IVC works fine - have tested connections. In fact, it’s all mostly working - I’ve been testing multiplayer (game & IVC) and it works fine. My only issue is that the server is rendering the graphics too.
The log shows:
[01/10/16 16:17:15] - Running wine- Launcher.exe -window LP_NUM_THREADS=4 (Working directory : /home/blacksheep/.PlayOnLinux/wineprefix/BMS/drive_c/Falcon BMS 4.33) fixme:heap:RtlSetHeapInformation 0x10000 0 0x23fcb8 4 stub fixme:ver:GetCurrentPackageId (0x23f700 (nil)): stub fixme:thread:start_thread Started native thread 0000002b fixme:thread:start_thread Started native thread 0000002c fixme:thread:start_thread Started native thread 0000002d fixme:thread:start_thread Started native thread 0000002e fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)"). fixme:win:EnumDisplayDevicesW ((null),0,0x23ed40,0x00000000), stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x347e210, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
so it looks as though only one of the 4 args are being picked up in the ‘commands to exec before’ section. I’ve had a look on your running server but can’t see any differences in the configs.
My loaded snd modules (host and container):
snd_seq_dummy 16384 0 snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi 32768 1 snd_seq_midi snd_seq 69632 3 snd_seq_midi_event,snd_seq_dummy,snd_seq_midi snd_seq_device 16384 4 snd_seq,snd_rawmidi,snd_seq_dummy,snd_seq_midi snd_dummy 24576 0 snd_pcm 106496 1 snd_dummy snd_timer 32768 2 snd_pcm,snd_seq snd 90112 6 snd_dummy,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_seq_device soundcore 16384 1 snd
and ALSA is installed. Not getting any errors when running:
aplay /usr/share/sounds/alsa/Noise.wav
and the dummy card is listed:
**** List of PLAYBACK Hardware Devices **** card 0: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7
so the soundcard appears to be working…
Cheers,
Del.
-
Hmmm just looking on your server too - I can’t see the graphs that the other DLLs provide and your launcher is only picking up the last part of those commands that should be exec’d before running the launcher.
If you put your server in to the 3d world, do you get the blank graphics?
Cheers,
Del.
-
The nogpu dll’s seems to be working as the screen turns black when enteing the 3d world.
If you not have installed the d3dx11 component please do so (PlayOnLinux -> Options -> Install components). I can’t remember if that was already installed when I started to write the guide. If that doesn’t help try using Wine 1.9 (PlayOnLinux -> Options -> Tab General -> Wine version 1.9.0-Staging). Maybe that does the trick and I see that this is not yet documented in the guide.
Regards
Blacksheep -
hmm… I’ve got everything running, however, when going into the 3D I get the 3d world… what am I missing?
I’m not working with Docker however, as I have an ESXi server, I just created a new 14.04 VM on it, and followed your path (xubuntu and everything).
-
Very likely the nogpu dll’s are not in the right location.
-
Bin64.
Not that complexStill nothing, however, I did try to add a shortcut for the x64 exe directly, however, it seems to be running the 32/bit. Anyway… Maybe that’s the problem… I’ll need to double check that…
-
Yes, the game should be started in 64bit mode. It crosses my mind that I have read somewhere that nogpu dll’s are 64bit only
-
Maybe a dumb question but could be possible that the attached file is empty?
I tried in window and linux and both are empty when I extract it.
-
Yeah, still not had time to upload the file. You can leech it now from https://www.dropbox.com/s/jkhalc1uy7dbls3/falcon_docker.zip?dl=0
Note that there is a prepared docker container at https://hub.docker.com/r/blacksheep70/falconbms-ubuntu1403/. Using this you need to
- execute
docker pull blacksheep70/falconbms-ubuntu1403
to install the docker container - logon via VNC and “download” the setup files for falcon 4, Falcon BMS and the nogpu dll’s from sthalik at https://db.tt/sHz2m7r8 into your docker image
- Then proceed starting with step 26
I will link the file in the guide too
Regards
Blacksheep - execute
-
The nogpu dll’s seems to be working as the screen turns black when enteing the 3d world.
If you not have installed the d3dx11 component please do so (PlayOnLinux -> Options -> Install components). I can’t remember if that was already installed when I started to write the guide. If that doesn’t help try using Wine 1.9 (PlayOnLinux -> Options -> Tab General -> Wine version 1.9.0-Staging). Maybe that does the trick and I see that this is not yet documented in the guide.
Regards
BlacksheepDefinitely did the d3dx11 step but couldn’t find that wine version in the dropdown. I’ll get it added and give it a go.
Cheers,
Del