From 6c10009e3967ff8657ccc527ab13c9894cffa6fa Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Mon, 25 Nov 2024 08:30:13 -0800 Subject: [PATCH] Fix registry container name in pruning cron job At some point docker compose changed the format of the container name for our registry. That meant the revert pulled up the old format which results in failures of this sort: Error response from daemon: No such container: registrydocker_registry_1 Update the name in the cronjob to the one currently reported by `docker ps` to fix this. Change-Id: I0f997d733084025535746f69685b319c86bb3f41 --- playbooks/roles/registry/tasks/main.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/registry/tasks/main.yaml b/playbooks/roles/registry/tasks/main.yaml index d8180a7ee7..bd68013e17 100644 --- a/playbooks/roles/registry/tasks/main.yaml +++ b/playbooks/roles/registry/tasks/main.yaml @@ -88,7 +88,7 @@ name: "docker registry garbage-collect" minute: "0" hour: "0" - job: "/usr/bin/docker exec registrydocker_registry_1 zuul-registry prune >> /var/log/registry-prune/prune.log 2>&1" + job: "/usr/bin/docker exec registry-docker_registry_1 zuul-registry prune >> /var/log/registry-prune/prune.log 2>&1" - name: Install logrotate rules include_role: