immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

Container digests change after release since around v2 #7871

New Issue
Closed
opened 2026-02-05 13:21:50 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 13:21:50 +03:00
Owner
Copy Link

Originally created by @aclerici38 on GitHub (Nov 20, 2025).

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

Ever since v2 released (or shortly after) something has been causing the server and ML containers' digests to change. I get container updates via renovatebot PRs which run hourly, I've noticed when I merge Immich updates within the first hour there's consistently been a second renovate PR after that just updates the container digests for the same tag. Here are some of the examples I've got, where I merged the update within an hour before renovate ran again:

https://github.com/aclerici38/home-ops/pull/1721 (2.1.0)
https://github.com/aclerici38/home-ops/pull/1828 (2.2.2)
https://github.com/aclerici38/home-ops/pull/1845 (2.2.3)
https://github.com/aclerici38/home-ops/pull/1931 (2.3.0/2.3.1)

Examples after issue created:
https://github.com/aclerici38/home-ops/pull/2131 (server)(2.4.0)

In both containers tagged 2.3.1, the about page in the immich ui (bottom left, click version) shows Build: 19524231183 and links to the same job. There seem to be no changes between the original/updated containers so functionally this isn't an issue, but I doubt it's intentional and causes some users who update immediately to have to re-pull the same containers again.

Thanks!

The OS that Immich Server is running on

NA

Version of Immich Server

v2.3.1

Version of Immich Mobile App

NA

Platform with the issue

  • Server
  • Web
  • Mobile

Device make and model

No response

Your docker-compose.yml content

NA

Your .env content

NA

Reproduction steps

  1. Pin immich containers to a digest
  2. update to newtag@digest within an hour after the release
  3. observe digest changing on same tag soon after

Relevant log output

Additional information

No response

Originally created by @aclerici38 on GitHub (Nov 20, 2025). ### I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. - [x] Yes ### The bug Ever since v2 released (or shortly after) something has been causing the server and ML containers' digests to change. I get container updates via renovatebot PRs which run hourly, I've noticed when I merge Immich updates within the first hour there's consistently been a second renovate PR after that just updates the container digests for the same tag. Here are some of the examples I've got, where I merged the update within an hour before renovate ran again: https://github.com/aclerici38/home-ops/pull/1721 (2.1.0) https://github.com/aclerici38/home-ops/pull/1828 (2.2.2) https://github.com/aclerici38/home-ops/pull/1845 (2.2.3) https://github.com/aclerici38/home-ops/pull/1931 (2.3.0/2.3.1) **Examples after issue created:** https://github.com/aclerici38/home-ops/pull/2131 (server)(2.4.0) In both containers tagged 2.3.1, the about page in the immich ui (bottom left, click version) shows `Build: 19524231183` and links to [the same job](https://github.com/immich-app/immich/actions/runs/19524231183). There seem to be no changes between the original/updated containers so functionally this isn't an issue, but I doubt it's intentional and causes some users who update immediately to have to re-pull the same containers again. Thanks! ### The OS that Immich Server is running on NA ### Version of Immich Server v2.3.1 ### Version of Immich Mobile App NA ### Platform with the issue - [ ] Server - [ ] Web - [ ] Mobile ### Device make and model _No response_ ### Your docker-compose.yml content ```YAML NA ``` ### Your .env content ```Shell NA ``` ### Reproduction steps 1. Pin immich containers to a digest 2. update to newtag@digest within an hour after the release 3. observe digest changing on same tag soon after ### Relevant log output ```shell ``` ### Additional information _No response_
OVERLORD commented 2026-02-05 13:21:52 +03:00
Author
Owner
Copy Link

@aclerici38 commented on GitHub (Dec 19, 2025):

Seems like only the server is being retagged now, not ML https://github.com/aclerici38/home-ops/pull/2131 https://github.com/aclerici38/home-ops/pull/2145

@aclerici38 commented on GitHub (Dec 19, 2025): Seems like only the server is being retagged now, not ML https://github.com/aclerici38/home-ops/pull/2131 https://github.com/aclerici38/home-ops/pull/2145
OVERLORD commented 2026-02-05 13:21:53 +03:00
Author
Owner
Copy Link

@aclerici38 commented on GitHub (Feb 4, 2026):

I can't track down where or how but it seems like this got fixed

@aclerici38 commented on GitHub (Feb 4, 2026): I can't track down where or how but it seems like this got fixed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#7871
Delete Branch "%!s()"

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?