Summary
The well-known image registry entry for chromium (forge-skills/registry/image-registry.yaml) was set to apt: chromium in PR #260, which is correct for the default Debian bookworm-slim base. On Ubuntu bases, however, chromium is a snap transitional stub that fails inside Docker (no snapd) — so a browser agent built on an Ubuntu base would install a broken browser.
The registry already models this base-image distinction for playwright via requires_ubuntu, but not for chromium.
Proposed fix
Make the chromium install base-image-aware:
- Debian →
apt: chromium
- Ubuntu → the real
.deb (e.g. a PPA / direct download), not the snap stub
Mirror the requires_ubuntu modeling already used for playwright, or add per-base apt package selection.
Context
Minor/nit from the PR #260 review. Non-blocking (the default base is Debian, where the current entry is correct), but worth its own change.
Summary
The well-known image registry entry for chromium (
forge-skills/registry/image-registry.yaml) was set toapt: chromiumin PR #260, which is correct for the default Debianbookworm-slimbase. On Ubuntu bases, however,chromiumis a snap transitional stub that fails inside Docker (no snapd) — so a browser agent built on an Ubuntu base would install a broken browser.The registry already models this base-image distinction for
playwrightviarequires_ubuntu, but not for chromium.Proposed fix
Make the chromium install base-image-aware:
apt: chromium.deb(e.g. a PPA / direct download), not the snap stubMirror the
requires_ubuntumodeling already used for playwright, or add per-base apt package selection.Context
Minor/nit from the PR #260 review. Non-blocking (the default base is Debian, where the current entry is correct), but worth its own change.