From fcb7673c310d684d8953a8f3021fb202e5d2220c Mon Sep 17 00:00:00 2001 From: Dorian Date: Tue, 21 Apr 2026 12:00:26 +0100 Subject: [PATCH] fix: pull_policy: build so portainer doesn't chase docker hub Portainer's "Pull and redeploy" runs `compose pull` before `compose up`. With `image: kaiser-natron:portainer` set, that tries to pull the image from Docker Hub and fails with "pull access denied" because the image only exists as a local build artifact. `pull_policy: build` tells compose to skip the pull step for this service. Co-Authored-By: Claude Opus 4.7 --- docker-compose.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index 6f09660..30ea4b2 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -14,6 +14,10 @@ services: context: . dockerfile: Dockerfile image: kaiser-natron:portainer + # Only build locally — never try to pull from a registry. Portainer's + # "Pull and redeploy" runs `compose pull` first, which would otherwise + # try to resolve `kaiser-natron:portainer` against Docker Hub and fail. + pull_policy: build restart: unless-stopped ports: - "5555:80"