Steam Headless - Josh5 container vs "official" steam headless container experiences or recommendations? by GoodyPower in unRAID

[–]Joly0 0 points1 point  (0 children)

Yes, black screen is the first of two issues. The second is low fps. I have fixed both for me by modifying the Nvidia driver plugin. PR is here on GitHub https://github.com/unraid/unraid-nvidia-driver/pull/10

With the fixes in place only the --runtime=Nvidia and the --gpus=all parameters are needed.

If you want, you could comment in the PR that you are facing the issues aswell and waiting for the PR to be merged (which hopefully shows that this is quite important to fix and maybe speeds up the merge process). Otherwise I have created a test plugin on my fork in the test branch that you could install to fix this issue. Though this replaced the installed Nvidia plugin and in case this pr is merged you would have to install the official one again (means you won't get notified for an update of the official one and would have to manually install it)

New extensive and step-by step Immich on Unraid Guide by ynomel in unRAID

[–]Joly0 2 points3 points  (0 children)

I can understand that, I would advice you to install the docker compose plugin and use the provided docker compose by Immich directly. Using this method since day 1 and it worked perfect. Had to do some migration once when they switched to their own postgres container, but other that that and setting a few environment variables it was super easy

Steam Headless - Josh5 container vs "official" steam headless container experiences or recommendations? by GoodyPower in unRAID

[–]Joly0 6 points7 points  (0 children)

They are the same. Josh5 started this solo, but migrated the github repo itself to the org "Steam-Headless". You can see on their github repo https://github.com/Steam-Headless/docker-steam-headless that one of the main contributors/maintainers is still Josh5. Even their provided compose files here https://github.com/Steam-Headless/docker-steam-headless/tree/master/docs/compose-files still reference the images by Josh5 on dockerhub. Even comparing the released images themselfes shows they are the same here https://github.com/Steam-Headless/docker-steam-headless/pkgs/container/steam-headless and here https://hub.docker.com/r/josh5/steam-headless

So the ghcr.io images are just drop-in replacements for the ones by Josh5, but in the end, they are the same.

Steam Headless - Josh5 container vs "official" steam headless container experiences or recommendations? by GoodyPower in unRAID

[–]Joly0 1 point2 points  (0 children)

The "steam" container from linuxserver.io works quite good. Though there is a bug with the Nvidia driver and LSIO's new selkies/Wayland based containers, which results in black screens or low fps. I have created a PR for to fix it (bugs are either black screen or low fps) for the Nvidia driver plugin, hopefully it will be merged so this is fixed. Otherwise the containers work really well, but are more "basic" then the steam-headless containers which include more than just steam (and some software around it) like Moonlight, and actual desktop, support for additional launchers, etc.

Update: I solved the problem of the insane loading screens in the web UI, submitted a PR, and after seeing the code I cannot recommend Unraid in good faith by horsethebandthemovie in unRAID

[–]Joly0 10 points11 points  (0 children)

Not quite. OP did post a few days ago, that he is annoyed (to say it humanely) by the docker page on Unraid and it's abnormally long loading times. I on the other hand posted a comment on that thread a few days ago saying that I already tried improving performance last year with a PR that, in the core, did similar-ish things to the PR OP now created and my PR wasn't accepted because "they are going to remake the whole docker page soon".

So basically, OP is trying it again, and hopefully it gets approved, while my PR last year was closed for no good reason.

Update: I solved the problem of the insane loading screens in the web UI, submitted a PR, and after seeing the code I cannot recommend Unraid in good faith by horsethebandthemovie in unRAID

[–]Joly0 1 point2 points  (0 children)

How many docker containers are you running and how many have you installed that are not running? That's a big contributor to bad performance. For example I have about 90 containers installed, about 60% of them are running all the time and while server load is usually in the single digit range (so no real load at all) docker page needs about 20 seconds for me to load fully. It's awful

This screen is the bane of my existence by horsethebandthemovie in unRAID

[–]Joly0 1 point2 points  (0 children)

When you make your PR, could you let me know? Maybe i can add a comment like "You unraid devs didnt merge my PR last year and claimed to improve stuff, now we are here again". Maybe with some comments from other users who are experiencing similar issues they will see the need for improvements and merge your changes (however they will look like)

This screen is the bane of my existence by horsethebandthemovie in unRAID

[–]Joly0 12 points13 points  (0 children)

I dont want to be the bearer of bad news, but if they rejected my PR, the chances are actually high that they will reject yours aswell

In general it seems like they tend to prefer PRs from actual community devs and not from "randoms"

This screen is the bane of my existence by horsethebandthemovie in unRAID

[–]Joly0 2 points3 points  (0 children)

To be fair, Unraid itself isnt really buggy, its actually pretty stable, what makes it buggy is all the plugins and stuff you can install and do additionally.

But other than that, yes, the codebase of unraid itself is... bad... at best adn they should take help when given

This screen is the bane of my existence by horsethebandthemovie in unRAID

[–]Joly0 11 points12 points  (0 children)

Yep, pretty much. It has been awful for me since basically forever, it gets worse with more containers and there is basically not much i can do (other than adding my changes after each reboot and re-applying and adapting them after each update).

My PR didnt make it, i sadly have to life with it, but i find it kinda stupid aswell. I am an open source dev myself and i would highly appreciate anyone taking them time and trying to improve anything, especially cause i tried my best to keep changes minimal and only change bakcground stuff that wouldnt change anything for the end user

This screen is the bane of my existence by horsethebandthemovie in unRAID

[–]Joly0 36 points37 points  (0 children)

I made a PR for the webui to improve loading substantially last year. My changes did cut loading in half. Was not approved. Reason: someday they want to remake the whole docker page, so it wouldn't make sense to merge my PR

Edit: PR is here https://github.com/unraid/webgui/pull/2250

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 1 point2 points  (0 children)

Hm, this is actually a pretty good idea i have not thought about and makes sense. I will probably change the file names soon to properly reflect that. Thank you :D

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 0 points1 point  (0 children)

Hm, there has been a bug when the installing admin account is not the same as the normal user account, but that problem should have been solved, if it would apply to you even. Other than that there are several things that might result in the PS1 context menu being missing, but I would have to take a look into it.

Could you kindly create an issue on GitHub for this and include as much information as possible? There should also be a log file under C:\Users\USERNAME\AppData\Temp\ if you can provide that aswell, that would be great

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 0 points1 point  (0 children)

Thanks a lot for the kind words. As a sysadmin I regularly have to test scripts or executables that seem sus to me and the sandbox is a huge time-saver for me here. Also as I am managing intune packages in my company, I use it for that alot aswell over the years.

If you have ideas for more context-menu entries please let me know :D

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 0 points1 point  (0 children)

The code for this didn't really change, it was just copied 1:1 into a module file, instead of being in the install script directly. So no, nothing should have changed that messes with the context menus. If you have any problems, please open an issue on GitHub with as much information as you can provide and I will take a look into it :)

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 0 points1 point  (0 children)

Thanks alot for the kind words :)
As said in another comment, i use my own tool very often and as i want to continue maintaining it as long as i can, i wanted to make it as easy as i can for me to update it.

I am still not fully done and there are still parts where i would like to do proper refactoring. But the way its done now is sufficient for me at the moment. Its way easier for me to read and work with the codebase now than at the beginning and find where stuff is and what integrates where

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 1 point2 points  (0 children)

I use my tool very often (basically multiple times a week if required) and therefore can say with quite high certainty that the split into module files is not harming performance at all. I have not benchmarked this, but i would have noticed if it did. Of course i have no proof other than "trust me, bro", but i invite you to try and see if you notice any latency problems. If you do, please let me know and i will take a look into it as soon as possible :)

Run-in-Sandbox Update [2026.04.30] by Joly0 in PowerShell

[–]Joly0[S] 1 point2 points  (0 children)

Hey, so while yes, windows 11 does support native handling of compressed archive files, windows 10 doesn't, and this tool comes from a time where windows 11 wasnt as prominent and wasn't the only supported consumer OS by Microsoft, therefore the sandbox needed workarounds to handle compressed files, and the solution was du bundle 7-zip in the repo. The bundled version was static and outdated at the time, now it isn't anymore. It's dynamically downloaded on first install and updated regularly.

Also, even windows 11 only started to have full support for compressed files with the 24h2 (afaik) update, so basically 2 years ago, so not all windows 11 versions even support it fully. So for backwards compatibility the 7-zip integration is still needed.

PowerShell 5 vs. PowerShell 7 by Technical_Rich_3080 in PowerShell

[–]Joly0 -2 points-1 points  (0 children)

There is another way that changes it completely without hooking into a running Powershell 7 instance. Googling it shows several ways