Chris Sherwood 98d235679e fix(docker): reject failed image pulls instead of treating them as success ... Every Docker pull went through `followProgress(pullStream, resolve)`, passing the Promise's resolve as dockerode's onFinished(err, output) callback — so the error argument was ignored and a failed pull (dropped/metered connection, bad manifest, registry error, disk full mid-pull) resolved as if it had succeeded. The code then tried to create/start a container from a missing or partial image, surfacing a confusing downstream error rather than the real cause. (#790) Add a DockerService.pullImage() helper that rejects when followProgress reports an error, and route all five pull sites through it: - service install - AMD ROCm image pull - service update - force-reinstall / recreate (forcePull) - sysbench benchmark image pull Closes #790 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-23 04:46:55 +00:00
..
controllers	feat(supply-depot): opt-in automatic updates for installed apps	2026-06-23 04:46:52 +00:00
exceptions	fix(Docs): documentation renderer fixes	2025-12-23 16:00:33 -08:00
jobs	fix(KB): stop ZIM ingestion progress freezing at 99% on multi-page archives	2026-06-23 04:46:54 +00:00
middleware	fix(API): skip compression for Server-Sent Events (#798)	2026-05-20 10:16:00 -07:00
models	fix(KB): stop partial_stall warning firing on atypical ZIMs (link-out/PDF-heavy)	2026-06-23 04:46:54 +00:00
services	fix(docker): reject failed image pulls instead of treating them as success	2026-06-23 04:46:55 +00:00
utils	fix(KB): stop partial_stall warning firing on atypical ZIMs (link-out/PDF-heavy)	2026-06-23 04:46:54 +00:00
validators	feat(supply-depot): opt-in automatic updates for installed apps	2026-06-23 04:46:52 +00:00