Docker Compose set to the major Version

[mathesst]

Hi there,

first of all thanks for this great App!

I just tried to set version Info in my .env file to "v1.140". But the docker compose pull then just went into error. I know there is a big warning about using watchtower in context of this app, but as far as i can see, every breaking change was on a major version. And i can live with that! But it would be great to use watchtower to update the minor versions, for the BugFixes.

Thanks!

BG Mathias

[bo0tzz]

v1.140 is not a valid version, it should be v1.140.0 or v1.140.1.

[mathesst]

Hi,

thanks for the fast response! Yes I figured that out as well, and leaves me with the question above.
So there is no way to but in a version string, so that every docker compose pull will just pull the latest minor version of this specific release?

Mathias

[skatsubo]

that every docker compose pull will just pull the latest minor version of this specific release

There is no such out-of-box option. With some extra scripting it can be emulated/implemented on your side.
But Immich docker images currently do not have "major" version tags like v1.140 or v1.141 if this is what you mean. So it's either "release" or full semver (major.minor.patch) "v1.140.1" and so on.

[mathesst]

Thanks for your answers, I will mark this as solved. Maybe I raise a feature request for this.
Mathias

[DonkeeeyKong]

Thanks for your answers, I will mark this as solved. Maybe I raise a feature request for this. Mathias

Since the devs plan to now follow semantic versioning with the stable release, I did a feature request for this here: #22556

[mathesst]

Thanks for creating the request! Already voted!

[DonkeeeyKong]

Thanks for creating the request! Already voted!

Thank you. My request was closed in favor of #4149. I don't know if you noticed that. :)