[GH-ISSUE #8500] [Feature] Explain skipped Hopper setup and verify container recovery on Bazzite #6627

Open
opened 2026-11-01 21:12:46 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Nov 1, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/8500

Before submitting

  • Searched open and closed issues and pull requests for related proposals.
  • Reviewed the contribution scope; this request does not approve native Bazzite installation support.
  • No credentials, private samples, or sensitive target data are included.

Area

Setup, packaging, or upgrade

Current limitation

On Bazzite, REA does not offer to install Hopper because the host is outside the automated installer's supported distribution list. Users can mistake the skipped offer for an Xvfb failure and start adding display-server workarounds that do not address it.

rea doctor only checks health. It never offers installation. rea setup can offer installation on supported hosts; redirected output and image builds disable interactive prompts.

The existing explicit refusal lists supported hosts and recommends configuring an existing provider, but does not guide a Bazzite user through a verified container workflow. This is a request for clearer explanations and a tested recovery path, rather than a claim that Bazzite should use Fedora's native installer.

Evidence and verification available so far

Executed the source parser at 245a581818ab13694fa438a06e39898ce03ab206:

parseLinuxDistribution('ID=bazzite\nID_LIKE="fedora"\nVERSION_ID=43\n', 'x64')
// { id: 'bazzite', versionId: '43', packageFamily: 'rpm',
//   hopperSetupSupported: false }

The same source accepts Fedora 43 x64 and Ubuntu 24.04 x64, and rejects Ubuntu arm64. Inspection of SetupPlan.ts and setupCommands.ts confirms that host support and terminal availability control the offer. Xvfb is checked later as a runtime dependency; REA starts its own authenticated private display.

These are source and parser results. NOT_ENOUGH_INFO: the original user's exact host image, architecture, Containerfile, and setup output were unavailable. No Bazzite/Podman installation or MCP session was reproduced locally.

Desired outcome and success criteria

  • Document why Bazzite gets no Hopper offer, how doctor differs from setup, and how to separate package verification from display/Python failures. Landed in 3842809c3.
  • Make the unsupported-host explanation easy to find in the setup result, including the detected distribution/architecture and the supported alternatives.
  • Verify and document a concrete x86-64 Ubuntu 24.04+ container workflow on Bazzite: install REA/Hopper together, expose a small test binary, run scoped doctor and analysis, and launch REA through OpenCode's MCP configuration.
  • State the tested host/image versions and remaining limitations. Keep Hopper optional and explain how to continue with an existing supported provider.

Expected interaction with targets

No target interaction for the explanation changes. The proposed manual container verification would read a selected binary and launch Hopper for analysis; it has not been executed.

Scope and alternatives

Preserve the unsupported-host boundary. Adding Bazzite to the mutable Fedora dnf install path needs a separate host-support decision and verification. Do not automatically create containers or start an extra global Xvfb :99 -ac server. A supported container is a proposed recovery route until the complete workflow is tested.

References

Originally created by @morluto on GitHub (Nov 1, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8500 ### Before submitting - [x] Searched open and closed issues and pull requests for related proposals. - [x] Reviewed the contribution scope; this request does not approve native Bazzite installation support. - [x] No credentials, private samples, or sensitive target data are included. ### Area Setup, packaging, or upgrade ### Current limitation On Bazzite, REA does not offer to install Hopper because the host is outside the automated installer's supported distribution list. Users can mistake the skipped offer for an Xvfb failure and start adding display-server workarounds that do not address it. `rea doctor` only checks health. It never offers installation. `rea setup` can offer installation on supported hosts; redirected output and image builds disable interactive prompts. The existing explicit refusal lists supported hosts and recommends configuring an existing provider, but does not guide a Bazzite user through a verified container workflow. This is a request for clearer explanations and a tested recovery path, rather than a claim that Bazzite should use Fedora's native installer. ### Evidence and verification available so far Executed the source parser at [245a581818ab13694fa438a06e39898ce03ab206](https://github.com/morluto/rea/tree/245a581818ab13694fa438a06e39898ce03ab206): ```ts parseLinuxDistribution('ID=bazzite\nID_LIKE="fedora"\nVERSION_ID=43\n', 'x64') // { id: 'bazzite', versionId: '43', packageFamily: 'rpm', // hopperSetupSupported: false } ``` The same source accepts Fedora 43 x64 and Ubuntu 24.04 x64, and rejects Ubuntu arm64. Inspection of `SetupPlan.ts` and `setupCommands.ts` confirms that host support and terminal availability control the offer. Xvfb is checked later as a runtime dependency; REA starts its own authenticated private display. These are source and parser results. NOT_ENOUGH_INFO: the original user's exact host image, architecture, Containerfile, and setup output were unavailable. No Bazzite/Podman installation or MCP session was reproduced locally. ### Desired outcome and success criteria - [x] Document why Bazzite gets no Hopper offer, how `doctor` differs from `setup`, and how to separate package verification from display/Python failures. Landed in [3842809c3](https://github.com/morluto/rea/commit/3842809c3). - [ ] Make the unsupported-host explanation easy to find in the setup result, including the detected distribution/architecture and the supported alternatives. - [ ] Verify and document a concrete x86-64 Ubuntu 24.04+ container workflow on Bazzite: install REA/Hopper together, expose a small test binary, run scoped doctor and analysis, and launch REA through OpenCode's MCP configuration. - [ ] State the tested host/image versions and remaining limitations. Keep Hopper optional and explain how to continue with an existing supported provider. ### Expected interaction with targets No target interaction for the explanation changes. The proposed manual container verification would read a selected binary and launch Hopper for analysis; it has not been executed. ### Scope and alternatives Preserve the unsupported-host boundary. Adding Bazzite to the mutable Fedora `dnf install` path needs a separate host-support decision and verification. Do not automatically create containers or start an extra global `Xvfb :99 -ac` server. A supported container is a proposed recovery route until the complete workflow is tested. ### References - [Bazzite container guidance](https://docs.bazzite.gg/Installing_and_Managing_Software/Containers/) - [Installation eligibility owner](https://github.com/morluto/rea/blob/245a581818ab13694fa438a06e39898ce03ab206/src/application/SetupPlan.ts) - [Distribution classification](https://github.com/morluto/rea/blob/245a581818ab13694fa438a06e39898ce03ab206/src/application/LinuxHopper.ts) - #7077 tracks the separate Fedora package/feed mismatch and download deadline; #3944 addressed unsupported-host installation advice.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6627
No description provided.