[GH-ISSUE #921] (Auto) Update not working? #7579

New Issue

GiteaMirror · 2026-04-27T21:27:44-05:00

GiteaMirror commented

2026-04-27 21:27:44 -05:00

Originally created by @n0r on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/921

@mbecker20 I have read through #781 and #851 but think this is not related. I noticed some strange behavior (in my case with immich).
The stacks are created as "Files on Server". The image definition is configured as follows:

docker-compose.yml:

[...]
immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
[...]
    env_file:
      - .env

.env file:

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

If I manually pull images via the ui it is not indicating that an update is available. It's the same when runnning the "Global Auto Update" schedule.
However if I change the compose file to image: ghcr.io/immich-app/immich-server:release bypassing the env file, komodo ui is immediately showing the update notification after a manual pull.

Additional info:

I assume that the env file is working correctly as I can successfully re-deploy the stack via komodo ui
Manual Pull / re-deploy works via komodo ui, after pushing the button the stack is updated and running with the new images

Am I overseeing something here?

Originally created by @n0r on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/921 @mbecker20 I have read through #781 and #851 but think this is not related. I noticed some strange behavior (in my case with immich). The stacks are created as "Files on Server". The image definition is configured as follows: docker-compose.yml: ``` [...] immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} [...] env_file: - .env ``` .env file: ``` # The Immich version to use. You can pin this to a specific version like "v1.71.0" IMMICH_VERSION=release ``` If I manually pull images via the ui it is not indicating that an update is available. It's the same when runnning the "Global Auto Update" schedule. However if I change the compose file to `image: ghcr.io/immich-app/immich-server:release` bypassing the env file, komodo ui is immediately showing the update notification after a manual pull. Additional info: * I assume that the env file is working correctly as I can successfully re-deploy the stack via komodo ui * Manual Pull / re-deploy works via komodo ui, after pushing the button the stack is updated and running with the new images Am I overseeing something here?

GiteaMirror commented

2026-04-27 21:27:47 -05:00

@CodigoBrew commented on GitHub (Oct 19, 2025):

Same issue here - 1.19.3 does not find its own Komodo updates nor updates for running stacks. Auto update seems to be broken.

@CodigoBrew commented on GitHub (Oct 19, 2025): Same issue here - 1.19.3 does not find its own Komodo updates nor updates for running stacks. Auto update seems to be broken.

GiteaMirror commented

2026-04-27 21:27:53 -05:00

@MrColumbo commented on GitHub (Oct 19, 2025):

i have not tracked since when it is working anymore but it was working fine and I could easily filter stacks on pending updates .....but for a couple of month it is not working anymore ....

@MrColumbo commented on GitHub (Oct 19, 2025): i have not tracked since when it is working anymore but it was working fine and I could easily filter stacks on pending updates .....but for a couple of month it is not working anymore ....

GiteaMirror commented

2026-04-27 21:27:58 -05:00

@Mazzelfassel commented on GitHub (Nov 4, 2025):

It stopped working for me when the auto update function was changed to a procedure. I had to manually recreate it and now it's partially working. It only detects updated for one stack. The remaining ones did not show any notifications. After looking up the remainding stacks manually they definetly had pending updates so I had to redeploy them by myself.

@Mazzelfassel commented on GitHub (Nov 4, 2025): It stopped working for me when the auto update function was changed to a procedure. I had to manually recreate it and now it's partially working. It only detects updated for one stack. The remaining ones did not show any notifications. After looking up the remainding stacks manually they definetly had pending updates so I had to redeploy them by myself.

GiteaMirror commented

2026-04-27 21:28:00 -05:00

@mbecker20 commented on GitHub (Nov 4, 2025):

Can you guys provide details about what you have tried?

For example, when the image contains environment var, you do need to deploy once with Komodo to initialize the interpolated image in cache. After this the updates should be picked up.

@mbecker20 commented on GitHub (Nov 4, 2025): Can you guys provide details about what you have tried? For example, when the image contains environment var, you do need to deploy once with Komodo to initialize the interpolated image in cache. After this the updates should be picked up.

GiteaMirror commented

2026-04-27 21:28:03 -05:00

@Mazzelfassel commented on GitHub (Nov 5, 2025):

Do you mean I should redeploy all my stacks after I updated the Komodo version? All my stacks were created in komodo (UI defined) and running there before and after the update. I have stacks with enviroment variables and for now I redeployed all active stacks. But for now I have to wait for one of them to have an update to check if it works.

@Mazzelfassel commented on GitHub (Nov 5, 2025): Do you mean I should redeploy all my stacks after I updated the Komodo version? All my stacks were created in komodo (UI defined) and running there before and after the update. I have stacks with enviroment variables and for now I redeployed all active stacks. But for now I have to wait for one of them to have an update to check if it works.

GiteaMirror commented

2026-04-27 21:28:07 -05:00

@Mazzelfassel commented on GitHub (Nov 9, 2025):

Today I checked again and no updates were detected or displayed. I have a paperless-ngx stack running and it got an update 3 days ago but nothing was displayed inside komodo. I manually redeployed the stack and confirmed that there was an update for it that should have been displayed.

This is the procedure relevant for triggering the update check, I had to manually create it because it was not created automatically when upgrading:

[[procedure]]
name = "Global Auto Update"
description = "Pulls and auto updates Stacks and Deployments using 'poll_for_updates' or 'auto_update'."
tags = ["system"]
config.webhook_enabled = false
config.schedule = "Every day at 03:00"
config.schedule_alert = false

[[procedure.config.stage]]
name = "Stage 1"
enabled = true
executions = [
  { execution.type = "GlobalAutoUpdate", execution.params = {}, enabled = true }
]

@Mazzelfassel commented on GitHub (Nov 9, 2025): Today I checked again and no updates were detected or displayed. I have a paperless-ngx stack running and it got an update 3 days ago but nothing was displayed inside komodo. I manually redeployed the stack and confirmed that there was an update for it that should have been displayed. This is the procedure relevant for triggering the update check, I had to manually create it because it was not created automatically when upgrading: ```toml [[procedure]] name = "Global Auto Update" description = "Pulls and auto updates Stacks and Deployments using 'poll_for_updates' or 'auto_update'." tags = ["system"] config.webhook_enabled = false config.schedule = "Every day at 03:00" config.schedule_alert = false [[procedure.config.stage]] name = "Stage 1" enabled = true executions = [ { execution.type = "GlobalAutoUpdate", execution.params = {}, enabled = true } ] ```

GiteaMirror commented

2026-04-27 21:28:09 -05:00

@kalikid021 commented on GitHub (Nov 10, 2025):

I'm also experiencing the same issue it seems once auto-update was moved to a procedure. I have about 60 stacks, and 35 servers, a majority of which have auto-update enabled in the stack config. Nearly all of these have UI-defined stacks, and are using the "Latest" tag for images.

Automatic polling is also enabled, and it seems there is no polling happening at all, I have started to discover stacks are out of date with the current version. If I click to pull images in the stack config, it pulls the images and automatically re-deploys the stack, however I have to now do this process manually per stack to pull updates.

This was a major draw for me migrating to Komodo, is being able to poll and manage automatic updates on service stacks I want to allow that procedure on, and now it is a manual process, and time consuming with dozens of stacks. If there is anything I can provide to diagnose this please ask. I love the product by the way.

@kalikid021 commented on GitHub (Nov 10, 2025): I'm also experiencing the same issue it seems once auto-update was moved to a procedure. I have about 60 stacks, and 35 servers, a majority of which have auto-update enabled in the stack config. Nearly all of these have UI-defined stacks, and are using the "Latest" tag for images. Automatic polling is also enabled, and it seems there is no polling happening at all, I have started to discover stacks are out of date with the current version. If I click to pull images in the stack config, it pulls the images and automatically re-deploys the stack, however I have to now do this process manually per stack to pull updates. This was a major draw for me migrating to Komodo, is being able to poll and manage automatic updates on service stacks I want to allow that procedure on, and now it is a manual process, and time consuming with dozens of stacks. If there is anything I can provide to diagnose this please ask. I love the product by the way.

GiteaMirror commented

2026-04-27 21:28:12 -05:00

@mbecker20 commented on GitHub (Nov 10, 2025):

@kalikid021 did you create and schedule the global auto update procedure? The point of this change is to bring this function into the foreground with more control. I understand this left a lot of users current setups without the automation to handle the auto update, it wasn't ideal but it is documented and easy to remedy, see https://komo.do/docs/resources/auto-update

@mbecker20 commented on GitHub (Nov 10, 2025): @kalikid021 did you create and schedule the global auto update procedure? The point of this change is to bring this function into the foreground with more control. I understand this left a lot of users current setups without the automation to handle the auto update, it wasn't ideal but it is documented and easy to remedy, see https://komo.do/docs/resources/auto-update

GiteaMirror commented

2026-04-27 21:28:13 -05:00

@kalikid021 commented on GitHub (Nov 10, 2025):

From your perspective, you have documented it, as far as you provided the TOML for a procedure to do global updates. I think from any random user's perspective the documentation is lacking, and when the changelog came through it wasn't clear what this change truly meant, which is the current behavior will stop immediately, and for that to continue you MUST add a procedure to do a global auto update.

Additionally you provide no instructions to accomplish this task in the UI, again just the TOML. There is no TOML editor in the UI, only read ability, and although the presumption is that the code could be placed anywhere in the main komodo TOML definition file, you don't provide a location. I personally would have to create an empty procedure, commit it via sync, and then look to see where that is, and then, clone, commit, push it to version control, then in the komodo UI perform a reverse sync to overwrite the running TOML config to add the procedure in the expected location in the TOML.

I'm not being overly critical in my personal opinion, but that whole process is not in the documentation, and if this is the way you intend it to be done, I would ask that you add that to the documentation so it's clear.

I have added the procedure however and will see if I in fact do get updates this afternoon, thank you for taking the time to try and address this.

@kalikid021 commented on GitHub (Nov 10, 2025): From your perspective, you have documented it, as far as you provided the TOML for a procedure to do global updates. I think from any random user's perspective the documentation is lacking, and when the changelog came through it wasn't clear what this change truly meant, which is the current behavior will stop immediately, and for that to continue you MUST add a procedure to do a global auto update. Additionally you provide no instructions to accomplish this task in the UI, again just the TOML. There is no TOML editor in the UI, only read ability, and although the presumption is that the code could be placed anywhere in the main komodo TOML definition file, you don't provide a location. I personally would have to create an empty procedure, commit it via sync, and then look to see where that is, and then, clone, commit, push it to version control, then in the komodo UI perform a reverse sync to overwrite the running TOML config to add the procedure in the expected location in the TOML. I'm not being overly critical in my personal opinion, but that whole process is not in the documentation, and if this is the way you intend it to be done, I would ask that you add that to the documentation so it's clear. I have added the procedure however and will see if I in fact do get updates this afternoon, thank you for taking the time to try and address this.

GiteaMirror commented

2026-04-27 21:28:14 -05:00

@mbecker20 commented on GitHub (Nov 10, 2025):

@kalikid021 Totally understood, PRs to the documentation are highly appreciated and you can help to fix this part, I have often said that my perspective is not ideal to create the documentation and I rely on user contributions here, its a really great place for new contributors to start as well as I focus on the core development.

@mbecker20 commented on GitHub (Nov 10, 2025): @kalikid021 Totally understood, PRs to the documentation are highly appreciated and you can help to fix this part, I have often said that my perspective is not ideal to create the documentation and I rely on user contributions here, its a really great place for new contributors to start as well as I focus on the core development.

GiteaMirror commented

2026-04-27 21:28:15 -05:00

@hellblue commented on GitHub (Nov 12, 2025):

how can i add this in my komodo installation? i have now version 1.19.5 upgrade over time since i have running it.

[[procedure]]

name = "Global Auto Update"
description = "Pulls and auto updates Stacks and Deployments using 'poll_for_updates' or 'auto_update'."
tags = ["system"]
config.webhook_enabled = false
config.schedule = "Every day at 03:00"
config.schedule_alert = false

[[procedure.config.stage]]
name = "Stage 1"
enabled = true
executions = [
  { execution.type = "GlobalAutoUpdate", execution.params = {}, enabled = true }
]

okay i think i have found it by myself under Procedures
i have added it now

@hellblue commented on GitHub (Nov 12, 2025): how can i add this in my komodo installation? i have now version 1.19.5 upgrade over time since i have running it. ``` [[procedure]] name = "Global Auto Update" description = "Pulls and auto updates Stacks and Deployments using 'poll_for_updates' or 'auto_update'." tags = ["system"] config.webhook_enabled = false config.schedule = "Every day at 03:00" config.schedule_alert = false [[procedure.config.stage]] name = "Stage 1" enabled = true executions = [ { execution.type = "GlobalAutoUpdate", execution.params = {}, enabled = true } ] ``` okay i think i have found it by myself under Procedures i have added it now <img width="1665" height="749" alt="Image" src="https://github.com/user-attachments/assets/33e28772-b57b-48b0-b622-cd11995300c0" />

GiteaMirror commented

2026-04-27 21:28:16 -05:00

@kalikid021 commented on GitHub (Nov 12, 2025):

Hope this helps you @hellblue

In the UI in the left pane under Resources, Click Procedures
Click New Procedure at The top of the page
Name your Procedure (Global Auto-Update) and click Create
Then click Add Stage
In the Execution Box Dropdown (None) Select "Global Auto Update"
Scroll down and under Schedule, in the Expression box type you preferred run schedule time based on the examples shown
Under Timezone, make sure to select your actual Timezone, as using the Default throws an error when attempting to save the procedure
Click save to complete the setup

@kalikid021 commented on GitHub (Nov 12, 2025): Hope this helps you @hellblue - In the UI in the left pane under Resources, Click Procedures - Click New Procedure at The top of the page - Name your Procedure (Global Auto-Update) and click Create - Then click Add Stage - In the Execution Box Dropdown (None) Select "Global Auto Update" - Scroll down and under Schedule, in the Expression box type you preferred run schedule time based on the examples shown - Under Timezone, make sure to select your actual Timezone, as using the Default throws an error when attempting to save the procedure - Click save to complete the setup

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#7579