[GH-ISSUE #115] Finish preparing Pegasus container #73

New issue

Open

opened 2026-10-15 12:55:55 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 12:55:55 +00:00

Owner

Originally created by @redbeardymcgee on GitHub (Sep 4, 2024).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/115

Currently the Pegasus container works great, but it is not complete. Documentation was added for the ROMs dir, but BIOS files have not been documented yet. Before simply adding documentation, I want to make sure we know how we intend to handle these files. Should this be lifted to the environment, such as WOLF_EMU_BIOS_DIR? Should it just be documented as a member of the mounts list in wolf's config.toml?

Additionally, Pegasus requires the user to prepare metadata files on their own. It is not packaged with any fetchers. I think we may use this one but should we add this to the container or document how to use it with wolf?

Hotkey configuration is also an important feature. Some way to at least exit the current emulator and return to the frontend is mandatory. This requires pre-configuration for each individual emulator, and 1 for retroarch as a whole.

Not all emulators require BIOSes, but some require different files that need to be installed or configured.

The launchers for the emulators themselves in Pegasus are important for getting to the emulator directly when needed. They should have some images associated and maybe other potential metadata if supported, to make them fit in with a launcher frontend.

Originally created by @redbeardymcgee on GitHub (Sep 4, 2024). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/115 Currently the Pegasus container works great, but it is not complete. Documentation was added for the ROMs dir, but BIOS files have not been documented yet. Before simply adding documentation, I want to make sure we know how we intend to handle these files. Should this be lifted to the environment, such as `WOLF_EMU_BIOS_DIR`? Should it just be documented as a member of the `mounts` list in wolf's `config.toml`? Additionally, Pegasus requires the user to prepare metadata files on their own. It is not packaged with any fetchers. I think we may use [this one](https://gemba.github.io/skyscraper/) but should we add this to the container or document how to use it with wolf? Hotkey configuration is also an important feature. Some way to at least exit the current emulator and return to the frontend is mandatory. This requires pre-configuration for each individual emulator, and 1 for retroarch as a whole. Not all emulators require BIOSes, but some require different files that need to be installed or configured. The launchers for the emulators themselves in Pegasus are important for getting to the emulator directly when needed. They should have some images associated and maybe other potential metadata if supported, to make them fit in with a launcher frontend.

bsakaguchi added the

documentation

enhancement

labels

2026-10-15 12:55:55 +00:00

bsakaguchi referenced this issue

2026-10-15 12:56:50 +00:00

[GH-ISSUE #194] Unhandled exception: Error during drmGetDevice for /dev/dri/renderD129, Invalid argument #128

bsakaguchi referenced this issue

2026-10-15 12:59:57 +00:00

[PR #86] [MERGED] Direct mouse and keyboard events without udev #352