Cesarinny Posted February 21 Share Posted February 21 On 9/15/2023 at 1:02 PM, enJOyIT said: Strange issue here... I click on "Play", it's checking Cloud Status and immediately stops and the "Play" Button reappears... Game obv. won't start. I am using a Nvidia A2000 Are there any log files I can check? The docker logs don't show any useful?! Any thoughts? Edit: Reinstalling the game worked... I'm also running an A2000, but not luck making de Docker running from it, how did you did it? Quote Link to comment
Nodiaque Posted February 21 Share Posted February 21 Try installing proton ge. Sometime, I had to toy with the option and bang it start working. Not all game work too Quote Link to comment
enJOyIT Posted February 21 Share Posted February 21 (edited) 3 hours ago, Cesarinny said: I'm also running an A2000, but not luck making de Docker running from it, how did you did it? Hi, try that extra parameter: --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart='unless-stopped' --shm-size='2G' --ipc='host' -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' --ulimit='nofile=1024:524288' --device='/dev/fuse' --device='/dev/uinput' --device-cgroup-rule='c 13:* rmw' --cap-add='NET_ADMIN' --cap-add='SYS_ADMIN' --cap-add='SYS_NICE' For me it's running fine with that. Edited February 21 by enJOyIT Quote Link to comment
Cesarinny Posted February 21 Share Posted February 21 Hi everyone! My Cache pool keeps filling up every time I run this container, despite already mapping the storage to a specific share. Any ideas on how to fix it? Quote Link to comment
Nodiaque Posted February 21 Share Posted February 21 Start by looking what is filling up. What folder take all the space. Then you will know where to look Quote Link to comment
Nodiaque Posted February 21 Share Posted February 21 7 hours ago, enJOyIT said: Hi, try that extra parameter: --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart='unless-stopped' --shm-size='2G' --ipc='host' -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' --ulimit='nofile=1024:524288' --device='/dev/fuse' --device='/dev/uinput' --device-cgroup-rule='c 13:* rmw' --cap-add='NET_ADMIN' --cap-add='SYS_ADMIN' --cap-add='SYS_NICE' For me it's running fine with that. Your missing a crucial extra param --runtime=nvidia Quote Link to comment
enJOyIT Posted February 21 Share Posted February 21 (edited) You're absolutely right 🙂 Copy/Paste lost it 😁 Edited February 21 by enJOyIT Quote Link to comment
Cesarinny Posted February 23 Share Posted February 23 (edited) Thanks! now my A2000 is working! Does anyone know how to make the default storage a share or a unassgnied device instead of my cache pool? Besides Steam i'm running Lutris in this container but can't install almost any current game once my cache pool only has 256gb, i've tried to map to a disk in my array and to my unassigned device but keeps using my cache as default storage. Edited February 23 by Cesarinny Quote Link to comment
Cesarinny Posted February 23 Share Posted February 23 using the steam app running on the container is it? Quote Link to comment
flipek87 Posted February 24 Share Posted February 24 Hello. After update to 6.12.8 docker don't want to start with connected nvidia graphics card. I found error like bellow: Verifying archive integrity... OK Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 550.54.14........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ WARNING: You specified the '--no-kernel-modules' command line option, nvidia-installer will not install any kernel modules as part of this driver installation, and it will not remove existing NVIDIA kernel modules not part of an earlier NVIDIA driver installation. Please ensure that NVIDIA kernel modules matching this driver version are installed separately. WARNING: Unable to determine the path to install the libglvnd EGL vendor library config files. Check that you have pkg-config and the libglvnd development libraries installed, or specify a path with --glvnd-egl-config-path. ERROR: Unable to delete existing file '/lib/firmware/nvidia/550.54.14/gsp_tu10x.bin' (Device or resource busy) ERROR: Unable to delete existing file '/lib/firmware/nvidia/550.54.14/gsp_ga10x.bin' (Device or resource busy) ERROR: Unable to delete existing file '/usr/bin/nvidia-smi' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/bin/nvidia-debugdump' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libcuda.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/bin/nvidia-cuda-mps-control' (Device or resource busy) ERROR: Unable to delete existing file '/usr/bin/nvidia-cuda-mps-server' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libcudadebugger.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/bin/nvidia-persistenced' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-nvvm.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-gpucomp.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-tls.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/etc/vulkan/icd.d/nvidia_icd.json' (Device or resource busy) ERROR: Unable to delete existing file '/etc/vulkan/implicit_layer.d/nvidia_layers.json' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-allocator.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvoptix.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-ngx.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvcuvid.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-encode.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libcuda.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-ptxjitcompiler.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-ml.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-nvvm.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-opencl.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libGLX_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-glcore.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-tls.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-glvkspirv.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-glsi.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-gpucomp.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvcuvid.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-encode.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-eglcore.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libEGL_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libGLESv2_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libGLESv1_CM_nvidia.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-fbc.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-allocator.so.550.54.14' (Device or resource busy) ERROR: Unable to delete existing file '/usr/lib/i386-linux-gnu/libnvidia-opticalflow.so.550.54.14' (Device or resource busy) Quote Link to comment
Dimtar Posted February 25 Share Posted February 25 21 hours ago, flipek87 said: Hello. After update to 6.12.8 docker don't want to start with connected nvidia graphics card. I just setup a new box with 6.12.8 and I think the same thing is happening to me. If I start the container it just goes into a restarting loop. If I ask Unraid to show me the logs it the popup window closes instantly. If I remove the nvidia part in extra parameters it works fine again. Quote Link to comment
Nodiaque Posted February 25 Share Posted February 25 Install old version driver in unraid, don't use latest. Quote Link to comment
flipek87 Posted February 25 Share Posted February 25 4 hours ago, Nodiaque said: Install old version driver in unraid, don't use latest. I tried and still nothing. With nvidia extra parameters container goes to restart loop. Quote Link to comment
cosmolotov Posted March 18 Share Posted March 18 I'm trying to get the sound to work through the secondary instance. The main one is working just fine through moonlight/sunshine and I can see the secondary instance and launch games and play them just fine, but there is absolutely no sound. I've tried a couple of games and also playing videos through the steam store page (which work on the main instance) but I hear nothing on secondary. Is there any configuration I have to do to get this working? Quote Link to comment
bigthrilla Posted March 20 Share Posted March 20 (edited) I've been searching through this thread and haven't had any luck finding info on getting an AMD igpu working other than radeon-top and remove the nvidia parameters. Anyone know of anything else to try or is that a known no-go. AMD 5700G. EDIT: Forgot to mention, have rebooted unRaid after changes to test/rule out as well. Thanks! Edited March 20 by bigthrilla Added info Quote Link to comment
fanta989 Posted March 23 Share Posted March 23 At first thanks very much to this projekt it works such great:) Is it normal when i start the container that all disk from the array spin up? I have no share or something from the array connected to the container. Its not a big problem but dont understand why. Quote Link to comment
RebelLion1519 Posted April 7 Share Posted April 7 Just set this up, for now just with integrated graphics till I get my GPU moved over into my server. Installed, connected to via Steam Link, but Steam says that no internet connection is available. Other apps within the container's XFCE desktop can get online. The container network setting is set to Host. Is there something else I need to configure or assign? Sorry, this feels like a stupid question. Quote Link to comment
Trick Posted April 18 Share Posted April 18 Hi all, I was wondering if there are some best practices with respect to performance in the docker? I notice some people saying it performs better than windows VM's. For me though, using an RTX3080 and 12 cores pinned from my 7950x performance drops quite significantly. I currently run about 60fps in GTA V max settings, 90fps in World At War max settings and maybe 20fps in Crusader Kings 3 all at 1440p. I recall getting atleast an average of 100fps on GTA V on 1440p ultrawide and atleast 70fps average on CK3 maxed out ultrawide. I have the storage directly set without /user/ as described in earlier posts. I use 8.0-5 in steam to be able to play the games. I also see that usually my GPU is only at about 30-40% load, my CPU also looks like it barely gets used all cores anywhere between 0-20% while running the game. Really hoping there is some way to decrease the gap between my VM and the Docker. That said, do really enjoy this docker and the ability to use my hardware as a cloud gaming server, thanks for making this docker! Quote Link to comment
Cloud779 Posted April 21 Share Posted April 21 Hi This is a nice docker an after some little complications, its work now perfect. I had only a question how can i update sunshine, there is a newer version out. Thanks Quote Link to comment
dmanwithers Posted April 24 Share Posted April 24 Brand new here. Running on the latest version of UnRAID. Docker works fine. My issue, I've got a system running 4600G and also have a RX 6600 dGPU. It sees both, and shows loaded drivers for the APU, but for the GPU says none. Because of this, the games aren't launching Quote Link to comment
nknr Posted May 16 Share Posted May 16 +1 on how to install EmuDeck and updating Sunshine Description mentions "one click install for things like EmuDeck" but I can't seem to find how 1 Quote Link to comment
JhonScript Posted May 21 Share Posted May 21 On 5/16/2024 at 12:10 PM, nknr said: +1 on how to install EmuDeck and updating Sunshine Description mentions "one click install for things like EmuDeck" but I can't seem to find how Hello, I can help you with how to update sunshine, It may not be the most optimal way, since it requires manually downloading the latest version, but it worked. 1. create "sunshine" folder in "/home/default/init.d" folder 2. download the file "sunshine-debian-bookworm-amd64.deb " of the page https://github.com/LizardByte/Sunshine/releases and store the file in the folder "/home/default/init.d/sunshine" 3. create "sunshine.sh" file in "/home/default/init.d" folder and in the content of the file it is this: cd /home/default/init.d/sunshine sudo apt install ./sunshine-debian-bookworm-amd64.deb 1 Quote Link to comment
JhonScript Posted May 21 Share Posted May 21 Hello, I am having a small problem with docker in unraid, I want to know if it is a known problem I am testing from the following clients "VM Windows 10" and "Fire TV" I have two gamepads connected to the client, "Dualshock" (I have also tested with a "Dualshock" and a "DualSense", the result is the same) The test is that I connect through "Moonlight" to docker, and I can only use one gamepad, I am verifying this with the page https://hardwaretester.com/gamepad (which I am running in Chrome, because they do not work in Mozilla Gamepads) The problem is that I press the buttons on Gamepad#1 and it reflects fine in the Chrome browser, from docker, but I press the buttons on Gamepad#2, it connects fine, but Gamepad#1 disconnects immediately. I have not been able to play local multiplayer on my emulator "EmulatorJS" which is also hosted as a docker on UnRaid (Which runs on the client in a Chromium-Based Browser) I already tested connecting a gamepad to the Fire TV client and another gamepad to the Windows client but the result is the same. I also ruled out that the problem was the clients, since I used the "Windows VM" as the Host with GeForce Experience and the client the "Fire TV" with the two gamepads, and it works perfectly. (This tells me that the problem is related to SteamHeadless Docker Sunshine) As additional information, my "SteamHeadless" docker does not have any graphics card associated with it since a GPU is not necessary to play the EmulatorJS emulator with a resolution lower than 800*600. The use cases for this are: 1. Make the EmulatorJS run on the server and not use the resources of the "low-end Android", "Fire Tv" client 2. Be able to play EmulatorJS multiplayer from the internet with friends, just by installing Moonlight on the clients Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.