Erich Blume
c86b5d7772
## Summary
- Move Dagger module from `.dagger/` to repo root (`src/blumeops/`), rename `blumeops-ci` → `blumeops`
- Replace opaque `docker_build()` with native Dagger pipelines that surface full build errors per step
- Migrate navidrome as the first container (`containers/navidrome/container.py`)
- Upgrade navidrome from v0.60.3 to v0.61.1 (major artwork overhaul, SQLite FTS5 search, server-managed transcoding)
- Add `dagger call container-version` for CI version extraction without Dockerfile parsing
- All mise tasks (`container-list`, `container-version-check`, `container-build-and-release`) updated for hybrid mode
- Legacy `docker_build()` fallback preserved for all other containers
## Motivation
When navidrome v0.61.0 added a new Go build tag (`sqlite_fts5`), `docker_build()` showed only "exit code: 1". We had to run `docker build --progress=plain` manually to find `undefined: buildtags.SQLITE_FTS5`. Native Dagger pipelines show the full error inline.
## Container build dispatch needed
After merge, dispatch container build for navidrome:
```
mise run container-build-and-release navidrome --ref 470b4bd
```
## Deploy steps
1. Wait for container build to complete
2. Back up navidrome-data PVC (non-reversible DB migrations)
3. `argocd app set navidrome --revision main && argocd app sync navidrome`
4. Verify at https://dj.ops.eblu.me
## Future
Remaining containers migrate incrementally in follow-up PRs using the same pattern.
Reviewed-on: #330
79 lines
3.6 KiB
Markdown
79 lines
3.6 KiB
Markdown
---
|
|
title: Add Container Version Sync Check
|
|
modified: 2026-04-11
|
|
tags:
|
|
- how-to
|
|
- containers
|
|
- ci
|
|
- zot
|
|
---
|
|
|
|
# Add Container Version Sync Check
|
|
|
|
Add a prek check that validates version consistency across the places container versions are declared: `container.py` VERSION constants, Dockerfile ARGs, `service-versions.yaml`, and nix derivations. The check enforces they agree.
|
|
|
|
## Context
|
|
|
|
Discovered during analysis of [[adopt-commit-based-container-tags]]: the new commit-SHA-based image tags need a reliable version source (`vX.Y.Z-<sha>`). Versions are currently scattered across Dockerfile ARGs (varying naming conventions), `service-versions.yaml` entries (many still `null`), and nix derivations (implicit from nixpkgs). A sync check ensures these stay consistent without adding a redundant fourth source.
|
|
|
|
## What Was Done
|
|
|
|
### 1. Created `mise run container-version-check` task
|
|
|
|
A typer-based uv-script that iterates over `containers/*/` and validates six rules per container:
|
|
|
|
1. Any `container.py` must declare `VERSION = "<value>"`
|
|
2. Any Dockerfile must declare `ARG CONTAINER_APP_VERSION=<value>`
|
|
3. Any `default.nix` must produce a version via `dagger call nix-version`
|
|
4. At least one build file must exist (`container.py`, Dockerfile, or `default.nix`)
|
|
5. A matching `service-versions.yaml` entry must exist with non-null `current-version`
|
|
6. All resolved versions from (1), (2), (3), and (5) must agree (v-prefix stripped for comparison)
|
|
|
|
Scoping: by default only checks containers changed vs main. `--all-files` checks everything. If `service-versions.yaml` itself changed, all containers are checked.
|
|
|
|
Blacklisted containers (utility images, not tracked services): `kubectl`.
|
|
|
|
Container-to-service name mapping: `quartz` → `docs`, `kiwix-serve` → `kiwix`.
|
|
|
|
### 2. Added prek hook
|
|
|
|
```yaml
|
|
- id: container-version-check
|
|
name: container-version-check
|
|
entry: mise run container-version-check
|
|
language: system
|
|
files: ^(containers/|service-versions\.yaml)
|
|
pass_filenames: false
|
|
```
|
|
|
|
### 3. Populated `service-versions.yaml`
|
|
|
|
Filled in `current-version` for all hybrid services: navidrome (v0.60.3), miniflux (2.2.17), teslamate (v2.2.0), transmission (4.0.6-r4), kiwix (3.8.1), forgejo-runner (0.19.11). Added authentik (2025.10.1) as a new hybrid entry.
|
|
|
|
### ntfy nix version skew (resolved)
|
|
|
|
The check discovered that ntfy's Dockerfile pins v2.17.0 but nixpkgs has ntfy-sh 2.15.0. This was resolved in [[fix-ntfy-nix-version]] by building a custom nix derivation from the forge mirror. The version check now extracts the version from local nix files via regex, falling back to Dagger for unmodified nixpkgs packages.
|
|
|
|
## Key Files
|
|
|
|
| File | Change |
|
|
|------|--------|
|
|
| `mise-tasks/container-version-check` | New: typer CLI sync validation script |
|
|
| `prek.toml` | Add `container-version-check` hook |
|
|
| `service-versions.yaml` | Populate `current-version` for all hybrid services + authentik |
|
|
|
|
## Verification
|
|
|
|
- [x] `mise run container-version-check --all-files` passes with no errors
|
|
- [x] Intentionally changing a Dockerfile ARG without updating `service-versions.yaml` fails the check
|
|
- [x] `service-versions.yaml` has `current-version` populated for all hybrid services
|
|
- [x] Nix-only container versions (authentik) checked via Dagger
|
|
- [x] ntfy nix version resolved via [[fix-ntfy-nix-version]]
|
|
|
|
## Related
|
|
|
|
- [[pin-container-versions]] — Prereq: containers need parseable version ARGs first
|
|
- [[add-dagger-nix-build]] — Prereq: nix version extraction
|
|
- [[fix-ntfy-nix-version]] — Prereq: ntfy nix derivation version skew
|
|
- [[adopt-commit-based-container-tags]] — Parent: CI uses the same version extraction at build time
|
|
- [[harden-zot-registry]] — Root goal
|