Automatic rebuilding of applications following git updates

[tiheger]

I have encountered an issue with the automatic update of my stack in Portainer, which is deployed via a GitHub repository. My Docker Compose file specifies that my application is built before deploying. Ideally, any change pushed to my GitHub repository should trigger a webhook to redeploy my stack in Portainer to incorporate the changes.

However, the problem I am facing is that after pushing changes to the repository, my Portainer instance does not rebuild the application as expected. Instead, it continues to use the old Docker image without reflecting the latest changes. To have the application rebuilt with the recent changes, I find myself having to manually delete the old image and redeploy the stack.

Is there a setting or a method by which Portainer can automatically detect that changes have been made and accordingly rebuild the image and update the stack without the need for manual intervention? Is such a feature perhaps being considered for future updates?

[Nick-Portainer]

Hey, can you give a breakdown of your compose and how it works so I can try replicate this as close to what you are doing?

[tiheger]

@Nick-Portainer any updates on a possible solution?

[Nick-Portainer]

When you setup your GitOps Stack, have you tried enabling the toggle "Re-pull image"? This will make sure to pull the latest version of the image specified in your compose file, so this will mean Portainer is always looking to pull and deploy with the latest image and won't use the old one as long as there is a new one avaliable.

[tiheger]

When you setup your GitOps Stack, have you tried enabling the toggle "Re-pull image"? This will make sure to pull the latest version of the image specified in your compose file, so this will mean Portainer is always looking to pull and deploy with the latest image and won't use the old one as long as there is a new one avaliable.

Already on and also the "Force redeployment" option is activated. The problem is that I dont pull a image because I build one local

[tiheger]

[tiheger]

HI @Nick-Portainer, sorry to bother you, have you looked for a possible solution? I need this to fix an important issue.

[yajith]

Just a theory, if you add an extra dummy VAR(ENV MYAPP_VERSION=1.0) to your Dockerfile as part of the next changes you are pushing to Git, does that change that trigger a rebuild?

[tiheger]

I dont think so, because the rebuild is triggered by the system, not by the application

[yajith]

what I was thinking is that adding such a dummy VAR would make the system to see that there has been a change in the Dockerfile itself and that in turn trigger a rebuild.

[tiheger]

Could be a solution, but is not the ideal way for my opinion

[yajith]

above is just trying to understand if the reason for no rebuilds triggering in your case is because Dockerfile is unchanged.

[tiheger]

above is just trying to understand if the reason for no rebuilds triggering in your case is because Dockerfile is unchanged.

Could be the reason, will try tomorrow. I think it checks if the image name exists and will skip the building.