[App Management][1.8.0] Plex update not offered: missing_version and scheduled registry manifest failures

Aperta
  • Qualcosa non va?
#633 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, shell
Ambito
devops

Direzione di ricerca

Start by tracing the application manager's repository-version update check and scheduled image-drift check; the report identifies missing_version and registry TOOMANYREQUESTS as separate failures, with no source files or tests named. Read the migration path for legacy app metadata and the update-detection entry points, then check existing tests for each failure. Done means the UI communicates failed or unknown checks, and the supported non-disruptive recovery path and relationship between the two update checks are clear.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What happened?

On ZimaOS 1.8.0, Plex Media Server reports that 1.43.5.11079 is available, but ZimaOS does not offer the Plex update in its Settings update interface. Plex itself is running; the problem being reported is update detection.

The application manager logs show two distinct failures:

  1. The repository-version update check rejects the installed Plex app with missing_version.
  2. Scheduled image-drift checks have failed to resolve the registry manifest with TOOMANYREQUESTS.

A later manual manifest query succeeded. These observations do not establish that either error alone explains the entire UI behavior.

Environment and installed metadata

  • ZimaOS UI reports: 1.8.0
  • Architecture: amd64
  • Container name: plex
  • Image reference: lscr.io/linuxserver/plex:latest
  • Installed LinuxServer build from the container log: 1.43.5.11029-6bf8af3f0-ls329
  • Environment: VERSION=docker
  • Ignore updates: off
  • Top-level Compose metadata includes:
    • x-casaos.id: org.icewhale.plex
    • x-casaos.repo_id: zimaos-appstore
    • x-casaos.store_app_id: plex
    • No top-level x-casaos.version field was found in the current exported Compose.
  • The official store's gh-pages/apps/org.icewhale.plex/meta.json, checked during diagnosis, reports version: 1.43.3; its Compose references lscr.io/linuxserver/plex:1.43.3. This is a separate catalog version from the running container's version.

The installation's original metadata/migration history has not been established.

Observed steps

  1. Run the existing Plex installation with the image and settings above.
  2. See an available server update in Plex.
  3. Open ZimaOS Settings: no Plex update is offered.
  4. Inspect the application-management log: the update list check logs a failure rather than a successful up-to-date verdict.

Relevant log excerpts

Selected entries from /var/log/casaos/mod-management.log on 2026-10-26 (UTC+03:00); unrelated apps and internal identifiers omitted.

At 23:00:42, zimaapp update check completed with failures included:

{"zimaapp_id":"zimaapp://v2app/plex","code":"internal","message":"repository update unsupported: repository version update is ineligible: missing_version"}

At 00:00:55, appstore maintenance image drift check completed with failures included:

app_id=plex
code=registry_failed
registry_failed: resolve remote image for service plex: GET https://lscr.io/v2/linuxserver/plex/manifests/latest: TOOMANYREQUESTS: retry-after: 1.086413ms, allowed: 44000/minute

Similar registry failures appeared on multiple earlier dates.

Read-only verification

Local image metadata is present, so this is not the empty-RepoDigests symptom described in #591:

sudo docker image inspect lscr.io/linuxserver/plex:latest --format '{{json .RepoDigests}}'

["lscr.io/linuxserver/plex@sha256:478be45a2abfafd618aba5d7d4c380b5e767414c1f02889ed5f91af9e95bafae"]

Later on the same date, this manual query succeeded:

sudo docker manifest inspect lscr.io/linuxserver/plex:latest

The returned OCI index included this amd64 manifest:

sha256:e95378a5a0bd141d7b827cb7391a4ea7eb9fe8b48c452102cebb71fbf79de78b

That differs from the installed amd64 digest. The registry error is therefore not continuous; the scheduled application-manager check and later Docker CLI query had different outcomes.

Expected behavior / requested guidance

  • Surface an update-check failure or unknown state instead of silently omitting the app.
  • Explain the relationship between repository-version updates and image-drift updates for an existing app using :latest.
  • Provide a supported way to repair missing version metadata or rerun detection without uninstalling, recreating, updating, or restarting the working Plex container.
  • Clarify whether missing legacy app metadata requires a migration fix, and whether the registry failures need separate handling.

No proposed metadata edit, image pull, container recreation, or Plex restart was performed during this diagnosis. The owner does not authorize experimental changes to the working server and is requesting a non-disruptive diagnostic or metadata-only recovery procedure. Full logs and screenshots containing local details have not been uploaded.

Lingua principale
Shell
Stelle
3.1k
Fork
130
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di IceWhaleTech/ZimaOS

Tutte le issue di IceWhaleTech/ZimaOS

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.