[FEAT] Support browser-free Ubuntu KDE builds for downstream images

Ouverte
#449 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
docker, shell
Domaine
build-system, devops

Piste de recherche

Start with the ubuntu-kde Dockerfile at the linked commit and compare both architecture Dockerfiles and copied root files for Chromium installation, desktop entries, wrappers, and launcher defaults. Review the existing build arguments and documentation to see how an Ubuntu-only browser-free option would fit. Done means the default build retains Chromium and a browser-free build skips its setup while preserving KDE and Selkies integration; the issue lists startup and runtime checks but reports none have been run.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement
Is this a new feature request?
  • I have searched the existing issues
Wanted change

Please provide a supported way to reuse Webtop's Ubuntu KDE/Selkies desktop integration without preinstalling Chromium, so downstream images can install Firefox or another application of their choice.

A browser-free build option would already address the immediate need. A reusable desktop-only build target/base image, with optional end-user applications added in a later layer, would be a useful longer-term option if it fits the project's maintenance model.

The existing published image should keep its current defaults. This request concerns the browser installed INSIDE the container, not the client browser used to access Selkies. It does not require publishing every desktop/browser combination.

Reason for change

The goal is a reusable Ubuntu + KDE + Selkies desktop foundation for custom images, including Firefox-only images, without maintaining a separate copy of the KDE session integration.

In the ubuntu-kde Dockerfile at 16efc927, Chromium is installed alongside the desktop packages, and its desktop entry is rewritten unconditionally. There is no browser-selection build argument in that file. This is a packaging feature request based on source/documentation review; I have not built or tested a proposed replacement image.

Alternatives considered:

  • Extending the published Webtop image and installing Firefox is convenient, but retains Chromium in the inherited image layers. Removing it in a later layer does not remove those original bytes.
  • baseimage-selkies with SELKIES_DESKTOP is a good lightweight option, but its labwc-based shell is not KDE Plasma.
  • Building KDE directly on baseimage-selkies is supported by the custom-image guide, but downstream projects must carry and track the desktop package selection, session scripts, and container-specific integration.
  • Dedicated browser images address single-application use, rather than reuse of the full Ubuntu KDE desktop.

I searched existing open and closed issues for browser, minimal, Chromium, and base-image requests and did not find an equivalent. If a maintained browser-free KDE build path already exists, a pointer to it would resolve this request.

Proposed code change

A small first step could be a build-time option such as INSTALL_BROWSER=true (proposed name, not an existing option), initially scoped to ubuntu-kde:

  1. Keep the existing Chromium behavior by default.
  2. When disabled, skip Chromium installation and its browser-specific desktop-entry/wrapper/default-launcher setup. Check both architecture Dockerfiles and the copied root files for references.
  3. Preserve the desktop/session integration and required runtime dependencies. Do not remove the xtradeb PPA unless it is verified unnecessary for all remaining packages.
  4. Document how downstream builds can add their own browser; a Firefox example for Ubuntu should use a suitable non-Snap distribution rather than assume apt install firefox provides a native package.

Alternatively, expose a named desktop build stage before optional applications are installed, and build the current full Webtop image from it. A published desktop-base tag would be helpful, but is not required for the first iteration.

Suggested acceptance checks: unchanged default build; successful browser-free build with Chromium absent from the package inventory; working KDE startup, menus, clipboard and audio in the flavor's supported display modes; and a downstream Firefox-only example. Any new argument should be clearly documented as build-time only, not a docker run environment variable.

There is no proposed patch or runtime validation yet. I would appreciate guidance on which scope the maintainers would prefer.

Langage dominant
Shell
Étoiles
4.5k
Forks
389
Merge moyen
21 h 52 min
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de linuxserver/docker-webtop

Toutes les issues de linuxserver/docker-webtop

Issues similaires

Plus d'issues Shell/Bash

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.