From f24eaa3f2371bc4a2dcb5726709a24d494809d26 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=92=D0=B8=D1=82=D0=B0=D0=BB=D0=B8=D0=B9=20=D0=A7=D0=B5?= =?UTF-8?q?=D1=84=D0=B0=D0=BD=D0=BE=D0=B2?= Date: Thu, 24 Sep 2026 17:36:40 +0300 Subject: [PATCH] Makefile: start the stopped build registry instead of waiting for it forever After a reboot the registry container exists but is stopped; docker inspect succeeded, nothing started it, and the readiness loop never ended. Co-Authored-By: Claude Opus 5.5 --- Makefile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 37bf8ea..7e3173f 100644 --- a/Makefile +++ b/Makefile @@ -57,10 +57,13 @@ base_images.yml: base-images: base_images.yml +# The container survives a reboot stopped, so it is started, not only created. build-registry: @docker inspect cluster-map-build-registry >/dev/null 2>&1 || \ docker run -d --name cluster-map-build-registry -p 127.0.0.1:5555:5000 -v cluster-map-build-registry:/var/lib/registry registry:2 >/dev/null - @until curl -sf http://$(BUILD_REGISTRY)/v2/ >/dev/null; do sleep 1; done + @docker start cluster-map-build-registry >/dev/null + @for i in $$(seq 30); do curl -sf http://$(BUILD_REGISTRY)/v2/ >/dev/null && exit 0; sleep 1; done; \ + echo "build registry on $(BUILD_REGISTRY) did not come up" >&2; exit 1 build: base_images.yml build-registry @test -n "$(VERSION)" || (echo "VERSION is required, e.g. VERSION=v0.7.0" && exit 1)