Make valkey local on ringtail (nix amd64) + bump to 8.1.7 #362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "valkey-nix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Weekly "make one non-local container local" pickup: immich-ringtail still pulled
docker.io/valkey/valkey:8.1.6because the existingcontainers/valkey/container.pybuild was arm64-only.containers/valkey/default.nix— nix-built amd64 valkey image, packaged by the ringtail nix-container-builder runner usingpkgs.dockerTools.buildLayeredImage. Mirrors the existingcontainers/authentik-redis/default.nixpattern.containers/valkey/container.pykeeps building the Alpine arm64 image for paperless on indri. Bumped both builds to upstream valkey 8.1.7 (Alpine 3.22 now ships8.1.7-r0; nixpkgs has 8.1.7).VERSION(upstream app) fromALPINE_PIN(apk pin) incontainer.pyso both build files can declare the same upstream version and passcontainer-version-check.service-versions.yaml: current-version 8.1.7, refreshed last-reviewed, upstream-source now points at the canonical valkey-io releases page.immich-ringtail/kustomization.yaml:docker.io/valkey/valkey:8.1.6→registry.ops.eblu.me/blumeops/valkey:v8.1.7-02859c5-nix, comment updated.paperless/kustomization.yaml:v8.1.6-r0-fabca04→v8.1.7-02859c5.Build
build-container run #563 — both jobs succeeded after a transient runner crash on the first dispatch (#562 build-nix), which surfaced two separate bugs that landed in a separate C0 on main:
runner-logssilently returned 0 with no output when the log file didn't exist on indrissh indriswallowing remote exit codes (fish login shell), which the wrapper now works around via a stdout markerTest plan
argocd app set immich-ringtail --revision valkey-nix && argocd app sync immich-ringtailargocd app set paperless --revision valkey-nix && argocd app sync paperless🤖 Generated with Claude Code