We know this sucks - Do not use this image

[thelamer]

If you need a web native version of steam we currently maintain https://github.com/linuxserver/docker-steam

If you want to only play games on devices that support Moonlight than use Games on Whales https://games-on-whales.github.io/wolf/stable/user/quickstart.html

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Look I get it this image barely works in some special situations.
I have been spending months now building up web native images for gaming and I am almost there. This will be a fully web native 60 fps gaming solution all in user space within the month.
I also have shared modes with secondary controller support for split screen stuff.

It's coming soon, just hold tight.

https://www.linuxserver.io/blog/webtop-3-0-part-1-a-call-to-revolutionize-web-based-linux-desktops

Expected Behavior

No response

Steps To Reproduce

Na

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

Na

Container logs

Na

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[ne0YT]

@thelamer
any ETA? :)

[thelamer]

Hard prerequisite linuxserver/docker-baseimage-selkies#5

[EtienneK]

I see webtop now supports /dev/dri. Does this mean SteamOS is coming soon?

[tejpillay]

@thelamer out of curiosity will controller support now work when using sunshine + moonlight?

[thelamer]

@thelamer out of curiosity will controller support now work when using sunshine + moonlight?

No, the controller interposer works specifically with our server.

My current plan is to make a vanilla steam image that is web only. No more remote play ports sunshine deps any of that just run steam like any other app.

If you are using sunshine you really should use https://github.com/games-on-whales/gow or something similar like https://github.com/Steam-Headless/docker-steam-headless.

These projects hook into the video card so the framebuffers never leaves it (lower latency among other big benefits) where our solution is all about userspace and delivering to a web browser while being compatible with stuff like kubernetes.

What is on my todo list is to see if I can do it without the seccomp and apparmor privs. Selkies and I have been bouncing around ideas about replacing the bwrap bins, but we are still focused on core rendering and hammering out all the different device issues right now.

I have not stated this before but in general do not use this image, it is not maintained and it is not going to go anywhere. I think the layering of jupiter/holo repos to make this is not worth it and just using the most compatible Debian/Ubuntu will work for more users.

[thelamer]

I did not even test Steam because I have been running 7x12s for over a month now an I know my obsessed ass will want to get this out.
It is a light lift for support I just need to build the interposers for 32 bit as well as some apps are elf64 some are elf32.

steam-example.mp4

This has always been the goal. I want to be web native with no host deps because the thing that all these steam containers have in common is support overload for host oddities and I cannot deal with that.

Again coming soon, but I have to invent the universe before making this particular apple pie, mostly because someone trying to run a game has a very different support burden than someone trying to run a cad or 3d rendering program. (they are usually non technical and just want to press buttons to make stuff work)