Selfhosted

39435 readers

1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Releasing Wolf: Stream virtual desktops and games running in Docker (games-on-whales.github.io)

submitted 1 year ago by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

Hello everyone! 👋

For the past year I had fun messing around with Docker containers, Moonlight/Sunshine and HW acceleration; so much so that I've ended up building a Gamestream server from scratch!

The basic underlying idea is to allow the followings:

Share a single server (possibly headless but doesn't have to be) with multiple users
by creating virtual HW accelerated desktops
whilst keeping remote mouse, keyboard and controllers completely separated
with low latency

It's still rough around the edges, and it needs more testing from the community; if you want to check it out, here you can read the docs and here's the Github repo.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 1 year ago (1 children)

What's required to map a folder into one of the containers (i.e. retroarch)? I've attempted to edit config.toml to include it, but the main wolf container immediately crashes on boot due to interrupt code 11. There's no other error messages, just a binary stack trace.

The folder exists. I've tried directly mounting the host path as well as mounting it into Wolf-Wolf-1 and using the local path, but nothing works. Even perfectly mirrored paths don't work. Wolf appears to be running as root so I don't think it's a permissions error? I can certainly access the folders. They are a locally mounted NFS, but I've used this with dozens of containers without issue.

[–] [email protected] 1 points 1 year ago (1 children)

It's probably failing to parse the config.toml file, although that should usually print a proper error line. Have you tried deleting the file or copy and paste the default?

[–] [email protected] 0 points 1 year ago (1 children)

Looks like the mount definitions require the :ro (or maybe :rq?) at the end unlike regular docker volumes, that was the issue.

[–] [email protected] 0 points 1 year ago

Ooops that was a lazy leftover from my side, sorry about that. Thanks for letting me know, I'll fix it soon!