• Posts

  • Joined

  • Last visited

  • Days Won


Josh.5 last won the day on January 10 2022

Josh.5 had the most liked content!

Recent Profile Visitors

5710 profile views

Josh.5's Achievements


Enthusiast (6/14)




Community Answers

  1. Yup. I'm still maintaining the current status. A few minor things are broken like the app install scripts, but so long as the container can run steam games, I'm happy. Users can follow instructions online to install lutris if they want it... Just to reiterate, I don't provide support in this forum any longer, all support and discussion happens on the discord server and is agnostic if unraid. If anyone wants to talk to me directly, you can come join us at The container has a pipeline to automatically fetch the latest updates once a week. That's why you are seeing docker image updates weekly without commits. Since I manage a bunch of open source projects, my time gets split across them, this one has not received any love for a few months as I moved and never setup my server at the new place until last week. I've been busy writing new applications and updating other projects. Eventually steam headless will get more dev time from me for new features.
  2. You cannot run this container in bridge network mode if you want to use inputs outside of steam big picture. Bridge will prevent things like controllers from working in game.
  3. I took a quick look into this. This is happening because steam is creating a drive link "Z:" to your root path "/" as a symlink. If you then view this from the host Unraid OS it looks like this: This is not something that the Steam Headless container is doing as much as it is what the Unraid host shares are doing. It has created a symlink to / and so if you brows that you will see all the things in your root filesystem. Hopefully this helps you in finding a solution that works for you. As for this container, there is not really any point in finding a fix. The solution as far as I can tell is to better configure your network shares for Unraid.
  4. This thread seems to be getting more popular this week.... I don't come here often to provide support. If anyone needs support fir anything from me, reach out to me on Discord through the link in the first post.
  5. I'm not following sorry. Are you able to share a video or something explaining what is happening?
  6. Would you be able to DM me on Discord to discuss your progress?
  7. Uinput plugin is no longer required in the latest Unraid release. I have never tried with Bluetooth devices. Only keyboard and mouse.
  8. I think it may be time to retire this lancache-bundle template. I have not been using it since I got access to fibre internet (which downloads games faster than pulling them back off the array). And the official monolithic docker image from lancache has come a long way since I created this bundle to combine everything into an AIO. While I really appreciate the $12 donation I received this year for maintaining the lancache-bundle docker image and this template, I probably will have to hang up my hat on it this month.
  9. I have not used the lancache container for a very long time. I tried to maintain it for people here who have been, but I cannot really test things and am flying under the assumption that things have been working fine for the people who have been using it. I'll probably be pulling the template from CA when I stop using Unraid next month as I have not intention of providing further support for it for this platform.
  10. You do not need a GPU to use Unmanic. That is a pretty outrageous statement to make. Using a GPU inside the official Unmanic Docker container is an optional thing that you can do if you wish. You can also use Unmanic on the VM that you have passed your GPU into if you like. Unmanic is a tool with a lot of capabilities of which only a very small sub-set would even have the option to take advantage of a GPU.
  11. Just as a notice here, I will soon be steeping away from using Unraid to develop and maintain my projects. I will still provide support for Unraid for all of my projects, but that will be moved and only provided via Discord with a focus of providing that support agnostic of the platform. Anyone wishing to reach out for any assistance or to provide any feedback should join us there. I will be focusing my future development on providing better compatibility for platforms that are not Unraid, and as such it makes no sense to remain here in this forum. I may still pop my head into this forum from time-to-time, but please do not expect support from myself from this thread going forward. Please move all support related questions to Discord.
  12. Don't unplug the other GPU. You need a GPU to use Steam Headless. You cannot use the GPU that you have isolated for the VMs. Without full logs, I cannot really say exactly what the issue is. You should also post any logs found in ~/.cache/logs inside the container.
  13. First post updated. You probably will find that you cannot use the GPU on the host for anything if it is being passed through to a VM. I'm pretty sure (but am not going to test this for you) that the NVIDIA docker runtime will not work without installing a NVIDIA driver on the host. Therefore, I'm pretty sure the linked documentation is correct for anyone who wishes to use Unmanic with the latest version of Unraid and a NVIDIA GPU.
  14. These are all games I downloaded from the steam headless container