Josh.5

To me that indicates that the plugin settings JSON has somehow gotten into an incorrect state. I did push a fix for something similar (which could also fix whatever is going wrong on your install) to the staging branch. You can check it out by changing "latest" to "staging" on your template. It should just work after that as it will revert an "null" values to defaults in the plugin settings (null is not a valid value ever, so it is strange that it even got there). Also, on a few other points that is suspicious.... settings #4 on the transcode videos plugin is the video encoder selector. What did you have selected (specifically interested in if are you using an NVENC)? NVENC has been reported to have issues on docker on Unraid. It seems like sometimes the container can lose access to the GPU from the NVIDIA docker runtime. I thought this was fixed a while back, but it is possible this is what is happening. The symptoms of this happening is that the transcode videos plugin no longer sees the NVIDIA GPU so files start failing to be trainscoded. When you then open the plugin settings, the NVENC options will dissappears and if you then close it, you will change the encoder config. I have never heard of this chaining it to "null" tho. Normally it reverts to one of the libx encoders.

@BVTJ Can you send me some screenshots of the issue and the Unmanic logs? Enable debug logging and restart Unmanic before reproducing the errors again. Then click "Download system logs" and send me those.

Have you tried restarting the container? The mist recent update of the transcode videos plugin was not compatible with the module reload and it kinda broke. But a restart if the app sets everything right.

EmuDeck can be installed by opening a terminal and entering: sh -c 'curl -L https://raw.githubusercontent.com/dragoonDorise/EmuDeck/main/install.sh | bash' When prompted to enter your password, just click enter (there is no password). When asked about the location, select a custom directory of your choosing. When asked about the OS or device, select Linux. Wait for ages as it just takes forever to install - especially on the array. I have removed the "one click" installation for things like Lutris and EmuDeck. I did not realise that was still in the docs. We have been maintaining our own set of init scripts for Steam Headless in the Discord chats which has automated setups for things like Retroarch and ESDE along with a bunch of other things. These init scripts are auto run during the container startup to ensure you emulators are up-to-date with the confing in github here: https://github.com/Steam-Headless/init.d . I personally would recommend using these init.d scripts and helping out on GitHub to build on them or maintain them over using EmuDeck if you are up for it.

I must have pasted this in there by mistake. Thanks for the heads up. I'll remove it as soon as i have time.

Have you also booted unraid in gui mode? This would also be wrong.

It is failing because you have. -v '/dev/input/':'/dev/input/':'ro' -v '/run/udev/data/':'/run/udev/data/':'ro' You have not updated your container template.

@MarianKoniuszkopost your docker run command. Looks symptomatic of you mounting /run/udev or /dev/input

I'll post a quick update here since there are people still coming here for support rather than discord. This weeks update adds some improvements to input devices. Your templates need to be updated to remove any mounts of /run/udev and /dev/input and you need ENABLE_EVDEV_INPUTS=true for mouse and keyboard support on moonlight. If you dont want to update, you can lock in docker tag :debian-0.1.0 rather than :latest. The easiest way to update your template is to just delete the docker container and reinstall it all from the apps tab.

Did you mention the other day that you installed a custom kernel on Unraid and your Denuvo games started working? If so, this tells me that something is missing from the Unraid kernel. Just to be clear, this is not an issue with the Steam Headless Docker image.

Not on the same GPU. This is something being looked into as time permits. (For better support or just for general discussions on future features in Steam Headless, join our conversation on discord. See link in first post of this thread.)

Ive decided that Kasm is not a good fit for steam headless. Id advise you to use moonlight for gaming and only use the web UI for managing the desktop as required. Ive forked NoVNC and have started working on some solutions of my own. But it will take a long time before they are ready. (For better support or just for general discussions on future features in Steam Headless, join our conversation on discord. See link in first post of this thread.)

This happens when you have an AMD or Intel GPU and you dont use an HDMI or DP dummy plug. (For better support or just for general discussions on future features in Steam Headless, join our conversation on discord. See link in first post of this thread.)

You need to enable privileged mode for now. This is something im still working on improving. (For better support or just for general discussions on future features in Steam Headless, join our conversation on discord. See link in first post of this thread.)

Thought I'd post a quick responce. First, jump on discord if you was support. Second, the latest builds have done away with the flatpak install of sunshine. This is now running it as an appimage and is being managed by the init process as a service. It will auto restart when it stops or crashes. The appimage does not have a tray icon showing for some reason. And the default browser is not set. So everything you described are a lot of very separate "issues".

This Docker image has been re-based to Debian Bookworm. This fixes a few issues with Flatpak mostly, but also gives us access to some newer packages. I have also tidied up the Arch based Dockerfile. This Arch variant will be classed as a "community variant" and I will not be providing support for it (There may very well be dragons). This Arch variant will soon be automatically built as "josh5/steam-headless:arch" and will have updates at the same cycle as the Debian version at "josh5/steam-headless:latest" and "josh5/steam-headless:debian". For this release of with Debian 12 Bookworm, Docker in Docker is available, but is missing 'nvidia-container-toolkit' because NVIDIA are not yet supporting Bookworm. If they do not fix that in the coming weeks, I will just explore using Debian 11's version of it.

Thanks. Yea. This was a decent update. I have been meaning to pivot the app installation for a while, but I never could get around to it. Moving forward, all "Apps" inside the container will be Flatpak first. Then Appimage. Then Docker (using Docker in Docker). And finally after those options I'll consider a installation via a script or deb package. Most of the cool things that we have on the Steam Deck are already either a Flatpak or an Appimage (Heroic, Lutris, Yuzu, Cemu, ProtonUp-QT, etc...). So to me this just makes sense. This also works better as it reduces the size of the Docker image and installs things to your `/home/default directory`.

Just a quick note here of some big changes in light of all of these issues... Today's builds contain the following changes: Fixed issues with latest NVIDIA drivers (tested on Unraid 6.11.5 - I am not upgrading again). Removes DISPLAY_DPI configuration. Fixes issues with multiple NVIDIA GPUs on your system. Many other tweaks to how our X server is running that may also benefit Intel/AMD users. Fixes issues with logging into Steam. Fixes issues with browsing to /mnt/games from Steam. Updates Steam installation to Flatpak. Automatically configure Steam with a second library pointing to "/mnt/games/GameLibrary/SteamLibrary" (change this as you like). Removes unused code for launching other display environments. Only Xfce4 will be supported from here on out. Tidies up Xfce4 menus - removing anything that was an eyesore or not necessary. Adds ProtonUp-Qt by default Adds a Software installation app to System > Software. Here you can install other Flatpaks like Heroic launcher and Lutris. Removes support for Sunshine (will be re-added later on as a Flatpak when I have time). Removes the "Installer - XXXXX" shortcuts from the menu for apps like Lutris and Heroic. Just install it from the Software app mentioned above. Replaces Firefox with a Flatpak installation. Removes old SSH code. This container does not support SSH. Fixes issues with some Appimages. Fixes issues with EmuDeck. This should now work exactly the same as it would on a Steam Deck. Heaps of code tidying up and deleting of things I don't want in there. Some further notes: It will take longer to start the container the first time after this update. You may open noVNC and just see a black screen... Just wait, it is just installing some Flatpaks to your home directory before starting Xfce for the fist time. Since Steam is now running as a Flatpak, you will need to configure it again. Sorry.

The downgrade process is simple enough and my initial impression for the past few mins is that there are not problems with it. I am not running any VMs so I cannot say anything about that. But for Docker containers and plugins, it is fine to downgrade to 6.11.5 as I have just done. All I did was: Download the 6.11.5 tar from their website. Put the USB stick in my PC. Create a backup of the whole USB stick. Extract the 6.11.5 tar on my PC. Copy everything EXCEPT for the `/config` directory to the USB stick. Safely remove the USB stick, put it back in the server and boot it. Profit... All issues are now resolved if you run the older NVIDIA driver.

Do not upgrade to Unraid 6.12. I cannot express enough how annoyed I am with the amount of time I've wasted this week upgrading my system to 6.12 to explore this issue. This is headache inducing. The OS version has so many underlying issues that are not at all related to Steam Headless and is preventing me from be able to even improve the container. Eg. issues with the mover. Issues with services like SSH just stopping outright, issues with Dockerd. I cannot stress enough, do not upgrade to 6.12.x. If you are on 6.12, then consider backing up your /config directory on your USB stick and downgrade back to 6.11. This is what I am doing at the moment.

For anyone having this issue with an NVIDIA GPU, this seems to only be affecting the latest driver. 530.41.03 and lower does not have this problem.

Looks like it may be related to this: https://github.com/ValveSoftware/steam-for-linux/issues/9730 I'll be looking into this issue this week. Will post here with updates as they happen. In the meantime, try that workaround by adding the flag for running the old UI.

I have the same issue now after upgrading to unraid 6.12. What version are you on?

Try forcing a re-create on the container

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 https://unmanic.app/discord 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.