fix: handle case where container does not exist during retire step

This ma happen during app renames, as the old versions of the containers will no longer be running.
This commit is contained in:
Jose Diaz-Gonzalez
2020-11-28 00:38:28 -05:00
parent 0786954d34
commit e8a532645f

View File

@@ -9,10 +9,12 @@ trigger-scheduler-docker-local-scheduler-register-retired() {
declare APP="$1" CONTAINER_ID="$2" WAIT="${3:-60}"
local IMAGE_ID
IMAGE_ID="$("$DOCKER_BIN" container inspect "$CONTAINER_ID" --format "{{.Image}}" | cut -d: -f2)"
fn-scheduler-docker-local-register-retired "image" "$APP" "$IMAGE_ID" "$WAIT"
IMAGE_ID="$("$DOCKER_BIN" container inspect "$CONTAINER_ID" --format "{{.Image}}" 2>/dev/null | cut -d: -f2 || true)"
fn-scheduler-docker-local-register-retired "container" "$APP" "$CONTAINER_ID" "$WAIT"
if [[ -z "$IMAGE_ID" ]]; then
fn-scheduler-docker-local-register-retired "image" "$APP" "$IMAGE_ID" "$WAIT"
fi
}
trigger-scheduler-docker-local-scheduler-register-retired "$@"