Fix navidrome custom container image v1.0.2 (#194)

## Summary
- Switch navidrome deployment from upstream `deluan/navidrome:0.60.3` back to custom image `registry.ops.eblu.me/blumeops/navidrome:v1.0.2`
- The v1.0.1 image was tagged before the `USER 65534` removal commit, so it still ran as a non-root user that couldn't write to the SQLite data directory
- v1.0.2 is built from current main which includes both the `zlib-dev` build fix and the non-root user removal

## Deployment and Testing
- [ ] Wait for CI to build `navidrome:v1.0.2` image
- [ ] Sync via ArgoCD and verify pod starts without CrashLoopBackOff
- [ ] Verify navidrome UI accessible at https://navidrome.ops.eblu.me

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/194
This commit is contained in:
Erich Blume 2026-02-16 08:24:33 -08:00
commit 74294094e3
3 changed files with 13 additions and 2 deletions

View file

@ -42,10 +42,13 @@ LABEL org.opencontainers.image.description="Navidrome is a self-hosted music ser
# Points to upstream canonical source, not the forge mirror used for builds
LABEL org.opencontainers.image.source=https://github.com/navidrome/navidrome
RUN apk add --no-cache ca-certificates tzdata taglib ffmpeg
RUN apk add --no-cache ca-certificates tzdata taglib ffmpeg \
&& addgroup -g 1000 navidrome \
&& adduser -u 1000 -G navidrome -D navidrome
COPY --from=build /navidrome /usr/bin/navidrome
EXPOSE 4533
USER 1000
CMD ["/usr/bin/navidrome"]