BlumeOps Docs

Pin Container Versions

1 min read

Pin Container Versions

Ensure every container has an explicit, parseable version declaration so that add-container-version-sync-check has something to validate against.

Context

Discovered during analysis of adopt-commit-based-container-tags: containers needed a uniform, parseable version declaration for the sync check. Most containers already had version ARGs (miniflux, navidrome, ntfy, etc.), but with inconsistent naming (NAVIDROME_VERSION, MINIFLUX_VERSION, etc.), and several containers (devpi, cv, quartz, nettest) had none.

What Was Done

Every container Dockerfile now declares ARG CONTAINER_APP_VERSION=X.Y.Z as its first ARG, providing a uniform parsing target. Containers that use the version in build commands chain it to a semantic ARG:

ARG CONTAINER_APP_VERSION=v0.60.3
ARG NAVIDROME_VERSION=${CONTAINER_APP_VERSION}

Specific changes:

  • devpi: Pinned devpi-server6.19.1 and devpi-web5.0.1
  • cv: CONTAINER_APP_VERSION=1.0.3 (matches latest Forgejo package release)
  • quartz: CONTAINER_APP_VERSION=1.28.2 (pinned nginx:1.28.2-alpine base)
  • nettest: CONTAINER_APP_VERSION=0.1.0 (internal, no upstream)
  • All others: Existing versions carried forward with new uniform ARG pattern

Key Files

FileChange
containers/*/DockerfileAdd ARG CONTAINER_APP_VERSION to all 13 containers
service-versions.yamlPopulate current-version for devpi, cv, docs

Verification

  • Every container Dockerfile has ARG CONTAINER_APP_VERSION=X.Y.Z
  • ARG chaining tested with Docker build (nginx:1.28.2-alpine)
  • devpi container pins pip package versions
  • cv version matches Forgejo package release (1.0.3)
  • quartz pins nginx base image to stable (1.28.2)

Graph View

Backlinks