forust
9b91b5847e
These five stacks still asked for :latest, but the build stopped pushing it - on main it only pushes main and prod, on dev only dev. Every one of these images therefore resolved only because the registry still had a stale :latest from before that change, and the next time one of them was actually built the reference would have dangled. Named for dtek-notif: of the seven, only that one still resolved at :prod, because it is the only image not rebuilt since the build dropped :latest - and it is the only one of these five stacks the deploy does not manage (no `active` marker, and its file is docker-compose.yaml, which the COMPOSE_STACKS glob does not even match). Touching dtek_notif/docker-compose.yaml matches dtek_notif/* in the build's changed-service detector, so pushing this builds it and publishes :prod for it too. Verified the other six resolve at :prod in the registry.
16 lines
292 B
YAML
16 lines
292 B
YAML
services:
|
|
dtek_notif:
|
|
build:
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
image: gcr.forust.xyz/forust/dtek-notif:prod
|
|
pull_policy: build
|
|
restart: unless-stopped
|
|
environment:
|
|
- TZ=Europe/Kyiv
|
|
dns:
|
|
- 1.1.1.1
|
|
- 8.8.8.8
|
|
networks:
|
|
- default
|