Josh.5

Members
  • Posts

    498
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Josh.5

  1. Try restarting the unraid server and then see if the controller works.
  2. Try checking the logs from the container's terminal: Using the GPU for transcodes in Plex will not be an issue. Plex does not use that part of the GPU.
  3. It's not vnc that is the issue. It is the Xserver. Your other containers are running a framebuffer Xserver. But they do not support GPU acceleration. This container is running an X11 server that supports your GPU, so it needs exclusive access to that hardware. If anything else is using that hardware, it will not start. When you show me the X server log I'll have a better idea. Take a look at the logs in /var/log/supervisor
  4. This image now supports AMD GPUs. I'll update the first post in the next few days with more details.
  5. Sorry, I have not tried to use the container for this reason. If you do figure it out, please post some details here so that others can also set theirs up in the same way that you are trying to.
  6. Usually the "Unable to connect to Unmanic backend..." disconnect message is being caused by your CPU working too hard and the web backend not getting a chance to respond before the timeout is reached.
  7. No, the hostname param will do nothing to solve this. However, you should be running the container on the host network. If you are running into issues, please first make sure you are using the most up-to-date template published in the CA store. Also be sure to follow through the setup guide in the first post of this forum thread.
  8. I have not yet setup the container to fake a real display yet. I personally am using an HDMI dummy plug.
  9. Are there any other services running on port 5901 I need to change that, but I suspect that could be the issue...
  10. Can you check the path :/.cache/log/audiostream*" for errors. Are you running the latest version of the container AND did you remove and re-install the template from CA?
  11. I would like to just quietly add that, while I have added the ports to the template, I only did so so that Unraid was aware of them and they would show for people wanting to check for port conflicts. Just so we are clear, running a container with net=host means the port mapping is pointless in the `docker run` command. The processes inside the container are on the same network interface as the host already. This is still something I am investigating, but for now I am setting that aside and I'm going to work on improving the overall experience of the container. I suspect with the new SteamOS coming up in just over a month we may see some nice changes and I want to be in a place where I can rebase this container (or create a second one) with these things.
  12. @[RIVINS] @Mobious Try google the error "Unable to load filesystem_steam.so". Looks like there are some issues with steam and XFS file systems for some games. I have not looked into this, but let me know if you find a fix that can be applied to the container or Unraid configuration.
  13. Dummy hdmi plugs are essential for this. Makes life some much simpler. The one I have reports a 4k resolution and cost about $4
  14. I have not tested yet, but it should be yes.
  15. Personally, I am having a lot of trouble getting something from Epic Games Store to work. I'm not much of a Linux gamer. Steam is pretty sweet and seamless, but these other things are kinda clunky and require that you know what to do or where to go for configuration docs. If anyone knows a good setup for legendary for the EGS, I would love to hear it...
  16. In order to keep the Docker image size below 3GB, I've decided to roll out installer scripts with the image. You can initialise these from the menu under Applications > Games. These installers will generate a installation script that will live in ~/init.d/* and will be executed on container startup. If you update the container image or modify the template settings, the install scripts will re-install the various applications next start of the container.
  17. First post updated with instructions on fixing up the controller input
  18. Hey team, Huge thanks to @ich777 for adding the uinput module to his list of plugins that he maintains (currently pending being added to CA). This has fixed controller support for this container on Unraid. I have updated the Unraid Docker template for this container. If you want to enable controller support with your Steam Remote Play, then, remove the container from your docker tab and then head back over to CA and re-install it. The template now has under the advanced section the ability to toggle the audio for the web interface on/off as well as a "Mode" configuration (mode is currently in testing and is not usable). Later on today / tomorrow I will update the initial post with instructions on installing that include the required uinput plugin
  19. I've installed among us and have tested it out. It does not work well with a controller input, but touchscreen input on my phone works perfectly (including the virtual touch controls).
  20. Have you got something modifying the permissions of the files in that directory?
  21. Lutris is coming... Along with Retroarch. I have been debugging and sorting out the controller issues this week. I have found the solution and am just working on the best way to get that to Unraid users. @ich777 has kindly offered to create a plugin that will add the required kernel modules to Unraid that this container needs to fix the controller issues. Once this is sorted I will publish an updated template in CA that will include all the new container features and a description in the first post of this thread of what needs to be installed.
  22. What version of the driver do you have on the host?