SeanFrank

Those who are having issues with this container crashing repeatedly, and never getting going, should consult this thread, it solved the problem for me: https://github.com/Steam-Headless/docker-steam-headless/issues/111 More specifically, xorg was crashing, and the container was not accessible. It was working fine for a while, and suddenly wouldn't run anymore a few months back. Scroll down to apclapp's comment. A real hero.

Thank you for looking into this. Sorry for my late reply. My concern is that the symlinks, and the folder containing the symlinks, were created by this container. I don't think this is an issue with my share config, as it hasn't changed in a long time, and the offending folder and symlinks didn't exist before I installed the Steam container. But now that I know they are symlinks, I can just clean them up. Thanks for taking time to look into it.

Thanks for your reply. Hopefully this will help. The only directory I mapped in the the Docker template is "/mnt/user/Software/" This is an Unraid share named "Software", which is shared with others. I told Steam-headless container to use this directory for steam games: /mnt/user/Software/RTP Games/Steam/ When a user browses the "Software" share, they can see all files on all devices in my Unraid system. Effectively exposing all files on the system to anyone with access to that share. They can open and edit. So they can just just browse all the way to: Software\RTP Games\Steam\steamapps\compatdata\1493710\pfx\dosdevices\ZSXKM0~L\mnt\disk1 Software\RTP Games\Steam\steamapps\compatdata\1493710\pfx\dosdevices\ZSXKM0~L\mnt\disk2 Software\RTP Games\Steam\steamapps\compatdata\1493710\pfx\dosdevices\ZSXKM0~L\mnt\cache etc Everything between "\Steam\" and "\mnt\" was generated by this container. \mnt\disk1,2,3 cache, etc, is every drive plugged into my system. You can then open these folders and see everything on every disk. I had the Nvidia Available devices setting set to "all" before. I JUST changed it and specified the GPU, and it didn't make a difference. But these links work when the container was not running, so it probably wouldn't help now. If I look at the file properties of this folder: Software\RTP Games\Steam\steamapps\compatdata\1493710\pfx\dosdevices\ZSXKM0~L\mnt my computer thinks it is much bigger than my total storage space, lol! Hopefully this helps clarify the issue. Whatever happens, thanks for your work on this container. It's the only way I managed to run any games on this system, after wasting far too many weekends trying to pass through a GPU to a VM.

I've run into an interesting issue where this container is exposing ALL files on my NAS to anyone who has access to the share it stores its games on. Here is an example of a folder that is exposed: S:\RTP Games\Steam\steamapps\compatdata\1493710\pfx\dosdevices\ZSXKM0~L\mnt\disk8\Media\Cinema S is a Network drive on my system. RTP games is where my game files live, and where this container keeps its steam directory. It's in the folder I mapped, referenced below. Anyone with access to this share, can access all files on every disk of my Unraid box. I checked the mapping on the container template, and I only gave it access to: /mnt/user/Software/ But somehow it can see every file on my Unraid box. And windows users can click through the share to see them. And the program Everything exposes them readily... This is very concerning. As a workaround, I'm going to create a new share, and put my Steam files there, and not give anybody access to it... But what could have caused this? I didn't give it any credentials. Maybe because its a Privileged application? I'm especially concerned that I'll delete something I don't want to, while I'm trying to clean this up...