Skip to content

image-building.md

Latest commit

 

History

History
67 lines (46 loc) · 1.89 KB

image-building.md

File metadata and controls

67 lines (46 loc) · 1.89 KB

Building and Pushing Container Images

All component images are pushed to a single repository on Quay.io, distinguished by tag:

Registry: quay.io/willirath/ostrea

Component Tag Dockerfile Build context
API ostrea-api-latest api/Dockerfile api/
Frontend ostrea-frontend-latest frontend/Dockerfile frontend/
Database (PostGIS) ostrea-db-latest database/Dockerfile.postgis-fedora database/
DB init ostrea-db-init-latest database/init/Dockerfile database/

Prerequisites

  • Docker with multi-platform support (buildx)
  • Write access to quay.io/willirath/ostrea
docker login quay.io

Build and push all images

Use scripts/build-images.sh. Each image is tagged with both latest and the current short git SHA:

bash scripts/build-images.sh
# → ostrea-api-latest, ostrea-api-<sha>, ostrea-frontend-latest, ...

With an optional suffix for environment targeting:

bash scripts/build-images.sh --suffix test
# → ostrea-api-latest-test, ostrea-api-<sha>-test, ...

bash scripts/build-images.sh --suffix staging
# → ostrea-api-latest-staging, ostrea-api-<sha>-staging, ...

The suffix can also be passed via SUFFIX env var:

SUFFIX=test bash scripts/build-images.sh

See oc-deploy.md for how to deploy with --set image.tag=latest-staging.

Helm chart integration

The chart pulls from the same registry via image.repository and image.tag in values.yaml:

image:
  repository: quay.io/willirath/ostrea
  tag: latest        # or a short git SHA like "abc1234"
  pullPolicy: Always

To deploy a pinned version:

helm upgrade ostrea ./helm/ostrea --set image.tag=abc1234

No registry changes needed between local (kind/MicroShift) and production (OpenShift) — all environments pull from Quay.io.