Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

bug(agents): agent launcher fails --publish-image on transient registry push timeouts

Aperta Adatta ai principianti
  • Qualcosa non va?
#4,884 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
76/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, shell
Ambito
devops

Direzione di ricerca

Inizia da scripts/agents/image.sh ed esamina deliver_agent_image, dove attualmente ce push interrompe l’avvio in caso di qualsiasi errore. Controlla la registrazione e la gestione degli errori esistenti nel launcher prima di scegliere un approccio con tentativi ripetuti limitati. Il lavoro è concluso quando gli errori transitori registrano ogni tentativo e possono essere recuperati, continuando comunque a stampare il riferimento dell’immagine fissato tramite digest; gli errori persistenti restano risolvibili e lasciano invariati sandbox e impostazioni.

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

Descrizione

Related to #3469. Found while running the registry delivery path from #4744.

User Story

I run gator against a remote Kubernetes gateway, publishing the tooling image with scripts/agents/run.sh --publish-image. I directly hit push failures that a retry would have absorbed, so that one slow layer upload doesn't throw away a completed build.

Problem Statement

--publish-image runs one ce push and fails the launch on any error (scripts/agents/image.sh, deliver_agent_image: ce push "$image_tag" || fail "image push failed"). Large layer uploads to Artifact Registry intermittently fail with net/http: timeout awaiting response headers. Each failure aborts the launcher after the image is already built and some layers are already uploaded.

Impact / Why This Matters

The gator tooling image is about 450 MB compressed. Two consecutive --publish-image --build-only runs failed on a different large layer each time. A plain docker push of the same local tag then succeeded on its second attempt. That means rerunning the launcher by hand until it works, or pushing outside the launcher and resolving the digest manually. Doing it by hand also bypasses the launcher's digest check.

Acceptance Criteria

  • A transient push failure is retried a bounded number of times before the launcher fails.
  • Each retry is logged with the attempt number and the underlying error.
  • After a successful retry, the launcher still resolves and prints the digest-pinned Tooling image: reference.
  • A persistent failure (for example an authentication error) still fails with an actionable error and no sandbox, provider, or settings changes.

Reproduction Steps

  1. Configure Docker auth for an Artifact Registry repository the user can push to.
  2. On an arm64 Mac, run DOCKER_DEFAULT_PLATFORM=linux/amd64 ./scripts/agents/run.sh --agent gator --gateway <gateway> --publish-image <region>-docker.pkg.dev/<project>/<repo>/gator:<tag> --build-only.
  3. Observe intermittent failed commit on ref "layer-sha256:…": … net/http: timeout awaiting response headers followed by error: image push failed.

Environment

  • OpenShell: launcher from #4744 (c8afb7321); gateway 0.1.6-dev.26+g229382e51
  • OS: macOS (arm64), Docker with buildx emulating linux/amd64
  • Runtime, deployment, or integration: Kubernetes compute driver on a managed cloud cluster; Artifact Registry

Suggested UX (if applicable)

openshell-agent-launcher: Publishing '…/gator:payload-13-7fa522fae'.
openshell-agent-launcher: push attempt 1/3 failed: timeout awaiting response headers; retrying in 5s
openshell-agent-launcher: Tooling image: …/gator@sha256:e88f5a66…

Logs

failed commit on ref "layer-sha256:eda61e0e…": failed to do request: Put "https://<region>-docker.pkg.dev/artifacts-uploads/…": net/http: timeout awaiting response headers
error: image push failed
Lingua principale
Rust
Stelle
17.1k
Fork
1.8k
Merge medio
2g 9h
PR unite (30g)
355

Preparare l'ambiente

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 NVIDIA/OpenShell

Tutte le issue di NVIDIA/OpenShell

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.