Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating with deployment tools does not work #6

Open
Solaris17 opened this issue Feb 24, 2023 · 4 comments
Open

Updating with deployment tools does not work #6

Solaris17 opened this issue Feb 24, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@Solaris17
Copy link

Solaris17 commented Feb 24, 2023

System: VM
OS: Ubuntu 22.04.1
Management: Portainer 2.17.1

Issue:

Even when the stack is configured to follow main and the box is checked to allow auto updates at interval portainer is failing to detect the new versions being published. Manually syncing does not fix the issue though the following snippet is provided:

Redeploy from git repository
This stack was deployed from the git repository https://github.com/rpgeeganage/ots-share-app.git .

Update docker-compose.bundle.yml in git and pull from here to update the stack.

It looks like some mechanism is missing for "docker-compose.bundle.yml" that may trigger software like portainer to pull the entire repo. Perhaps a version?

Keep up the fantastic work.

@rpgeeganage rpgeeganage added the bug Something isn't working label Feb 25, 2023
@rpgeeganage rpgeeganage self-assigned this Feb 25, 2023
@rpgeeganage
Copy link
Owner

@Solaris17 ,
I think you can set a tag name.
e.g: refs/tags/2.2.0
Instead of refs/heads/main.

@Solaris17
Copy link
Author

hm, I guess that would really depend on how you want people to handle updates. If they want to feature lock that would make sense; if they want to be continuously in feature parity though that would be problematic imo.

@rpgeeganage
Copy link
Owner

@Solaris17 ,
sorry for the late reply. Do you have any project which I can refer to so I can modify this based on your suggestion.

@Solaris17
Copy link
Author

No worries @rpgeeganage I was referring to portainers ability to do this during stack deployment. I don't have an example; just a use case. That being that if you wanted your containers to continuously track they would update themselves. Before this option existed, and outside of portainer, this was generally done with watchtower.

Here is portainers take on how this option functions. I grabbed the section anchor, but the rest might be worth the read.

https://docs.portainer.io/user/docker/stacks/add#automatic-updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants