CI: a container job that starts seconds after the dev image is pushed cannot pull it
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- docker, github-actions
- Domínio
- ci-cd
Direção de pesquisa
Start with ci.yml and the build dev/ci image job, then read tools/ci_tier_check.sh and its self-test. Compare the proposed pull check, attestation handling, and longer retry against the failure logs; the issue requires recording one choice and its reason. Done when the chosen check is logged on pull request, merge group, and dispatched runs, the tier check passes, and the requested Actions API count is added here.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Seen on a dispatched full lane, run 44020220329 (ci.yml, lanes=all, on a branch at 5092ba79), 2026-11-17.
What happened
The job build dev/ci image pushed ghcr.io/inauguralsystems/eigenscript-dev:ci-5092ba79… and ended at 04:55:29Z. Four container jobs that need it started between 04:55:31Z and 04:55:40Z, and each failed in its "Initialize containers" step before any step of ours ran:
docker pull ghcr.io/inauguralsystems/eigenscript-dev:ci-5092ba793fbc4761cd5e1959e349d79ee086f65e
Error response from daemon: failed to resolve reference "ghcr.io/…/eigenscript-dev:ci-5092ba79…"
##[warning]Docker pull failed with exit code 1, back off 9.658 seconds before retry.
failed to copy: httpReadSeeker: failed open: could not fetch content descriptor
sha256:6a8f0165885b4a4dedec34bb6adf8d127f561ec2eb626133159ce8d02cc568e5 (application/vnd.in-toto+json) from remote: not found
##[warning]Docker pull failed with exit code 1, back off 8.734 seconds before retry.
Error response from daemon: failed to resolve reference "ghcr.io/…/eigenscript-dev:ci-5092ba79…"
##[error]Docker pull failed with exit code 1
The failed jobs: db extension (postgres service), db extension suite (postgres service), extensions / server (http+net+gfx) and ancillary checks, replay differential (same-binary tape fidelity); and extensions (http+net+gfx suite; embed/lsp/jit-smoke) after them, as their aggregate. The container jobs that started later in the same run pulled the same tag and passed. The change under test was documents only.
What it looks like
The tag resolves a few seconds after the push returns, and the blob the second attempt could not fetch is the attestation that docker/build-push-action adds to the image index. The runner tries three times in about twenty seconds and gives up. So a job that is scheduled at once after the image job can lose a race with the registry.
Done when
- Decided and recorded here: the image job proves the tag can be pulled before it ends (a pull by the pushed digest with a bounded retry), or the image is pushed without the attestation manifest, or the container jobs get a longer retry. With the reason for the one chosen.
- The image job's log shows the check that was chosen, on a
pull_requestrun, amerge_grouprun and a dispatched run. -
tools/ci_tier_check.shpasses with the change, and its self-test covers the new step if it adds one. - A count from the Actions API, in this issue: of the last 200 runs of
ci.yml, how many had a container job fail in "Initialize containers" with this message. That says how often the race is lost today.
— Claude DevBox
- Linguagem predominante
- C
- Estrelas
- 3
- Forks
- 7
- Merge médio
- 3h 28min
- PRs com merge (30d)
- 270
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Inclui um Dockerfile ou arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de InauguralSystems/EigenScript
-
area:gates kind:gate-defect
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
InauguralSystems/EigenScript#2476 ·
Mantenedores costumam responder em até 1 dia
-
area:gates needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
InauguralSystems/EigenScript#2462 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
The hosted-RNG check refuses a clean tree that has a tracked file with a double quote in its nameAbertaarea:gates kind:gate-defect needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
InauguralSystems/EigenScript#2461 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
area:gates kind:gate-defect needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
InauguralSystems/EigenScript#2458 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
`http_post`: `headers` text with something after its JSON value now means no headers, without a wordAbertaarea:http kind:silent-wrong
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
InauguralSystems/EigenScript#2394 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de InauguralSystems/EigenScript
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 92/100
flipperdevices/flipperzero-firmware#4520 ·
Mantenedores costumam responder em até 1 dia
-
area/build-framework kind/enhancement priority/low
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
yugabyte/yugabyte-db#38826 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
meshcore-dev/MeshCore#3891 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
vlang/v#32675 · 1 comentário ·
Mantenedores costumam responder em até 1 dia