search

azukaar / Cosmos-Server

☁️ The Most Secure and Easy Selfhosted Home Server. Take control of your data and privacy without sacrificing security and stability (Authentication, anti-DDOS, anti-bot)
https://cosmos-cloud.io
Other
3.44k stars 118 forks source link

[BUG]: Docker-compose files does not update when serv-app is updated #256

Closed hgpuke closed 2 months ago

hgpuke commented 4 months ago

What happened?

I use Immich as one of the serv-apps. It has undergone several updates since I first installed it. Back then, it was 1.098, now it is 1.105. Regardless, if I go to the container details page and look at the compose-code, it states that it is still running 1.098 which is not true. The web-ui of the app clearly states 1.105.1.

What should have happened?

I should have seen version 1.105.1 in the composer file, or :latest

How to reproduce the bug?

  1. Install a serv-app
  2. Note down its container version
  3. Wait until it updates
  4. Note its new container version
  5. Go to the container details page in Cosmos and then to compose-file
  6. Look at version number there. Clearly the compose file is not reflecting reality

Relevant log output

No response

Other details

What else is not updated when a serv-app is updated?

System details

azukaar commented 2 months ago

I am assuming that you are updating Immich without updating the container's tag. Because if your image is say Immich:1.2.3 in the compose, then Cosmos will not even update it (because the version is frozen). If your image is Immich:latest, or Immich:1 only then will it be updated by Cosmos.

Otherwise, may be you are referring to some env var not updating properly (as opposed to the image name) to which there's not much I can do. The compose is ALWAYS up to date because it is literally generated dynamically when you navigate to the compose tab based on the container's true state.