-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[QUESTION] How to update using docker-compose? #294
Comments
Heya @mfnalex - Thank you for your kind words 😊 So I wrote some docs on how to update Docker containers, which you can find here. I think in your situation, the easiest method is going to be to use WatchTower. But if you want to do it manually, then just kill of the existing container, and pull down the latest image, then restart the existing container. Maybe something like this:
I push updates a few times a week, so updating manually might get a bit annoying. |
Hello, You can also start Watchtower manually this way so it will see if an update for Dashy is available, if so it will upgrade and then shut down ( --rm argument) :
|
Thank you! Somehow I couldn't find the existing docs, sooo thanks again :D |
This comment has been minimized.
This comment has been minimized.
Is it correct that Watchtower also works for Docker compose? Sorry to steal your time, I'm a total docker noob, but to me it looked like Watchtower only works for "regular" docker containers that were pulled from the hub, and not for "composed" containers. |
Watchtower works for all containers. |
Hey @mfnalex - Thank you so much for your sponsorship 💖It's super kind of you :) |
Thanks for the answer, I think I got it working now :3 |
Hi :)
Thanks for this awesome software! I've been looking for something like this for weeks! Now, to my question :D
How can I update from 1.8.7 to 1.8.8 using docker-compose? I did
docker-compose stop
and thendocker-compose up -d
and thought it will now use the newest version, but it doesn't. I'm not really familiar with docker, so any help would be appreciated :)The text was updated successfully, but these errors were encountered: