sirius/osint-dashboard
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ci: pin db image instead of rebuilding in CI
All checks were successful
build-and-deploy / build (push) Successful in 2m14s
Details

Browse source 
Dockerfile.pg installs TimescaleDB from packagecloud.io, which the Pi's
network cannot reach (ISP abuse-mitigation blackholes AWS ranges after the
masscan incident). Every CI deploy rebuilt the DB image and failed on the
packagecloud fetch, blocking all pipelines.

The DB image is now built once manually (docker compose build db) and
pinned as localhost/osint-dashboard-pg:latest; compose up uses it directly.
The app build only needs deb.debian.org + pypi + the docker daemon's
registry mirror, all reachable.
This commit is contained in:
Sirius DevOps 2026-08-27 18:26:57 -04:00
parent 50d3dbb1dc
commit 47628cc5f2
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docker-compose.yml
View file

@ -14,10 +14,13 @@ name: osint-dashboard
services: services:
db: db:
build: # NO build: block here on purpose. The DB image (TimescaleDB+PostGIS) is
context: . # built once via Dockerfile.pg and pinned as localhost/osint-dashboard-pg.
dockerfile: Dockerfile.pg # Dockerfile.pg installs TimescaleDB from packagecloud.io, which some
platforms: ["linux/arm64"] # networks (and ISP abuse-mitigation blackholes) block, so rebuilding it
# on every CI deploy made the pipeline flaky. Rebuild manually when the
# base image or extensions need bumping:
# docker compose build db && docker compose up -d db
image: localhost/osint-dashboard-pg:latest image: localhost/osint-dashboard-pg:latest
container_name: osint-db container_name: osint-db
restart: unless-stopped restart: unless-stopped