# How to upgrade docker-compose.yml in a running Stack

**URL:** <https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370>\
**Category:** Rancher 1.x\
**Created:** [January 31, 2017, 8:39pm UTC](https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370 "2017-01-31T20:39:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![predmijat](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/predmijat/32/2091_2.png) [@predmijat](https://forums.suse.com/u/predmijat)\
**Post date:** [January 31, 2017, 8:39pm UTC](https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370/1 "2017-01-31T20:39:40Z")

</div>

Hi,

I’ve created a Stack by providing a `docker-compose.yml`. I see that there’s an `Upgrade` button next to each container, but as far as I understand how this works it’s no use - each service in compose file has a specific version assigned.

What I would like is to update the `docker-compose.yml` file, and redeploy (Upgrade) only those services (containers) which have new version.

Does that make any sense? 🙂

Thanks!

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [January 31, 2017, 9:27pm UTC](https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370/2 "2017-01-31T21:27:41Z")

</div>

What your saying makes sense but is not there. The UI has yaml import as a one-time convenience to get a stack into the UI. If you want to continually work with yaml file use the CLI/compose tools where you have tools to edit and compare them; working with yaml in a browser is not pleasant.

---

<div class="post-metadata">

**Author:** ![predmijat](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/predmijat/32/2091_2.png) [@predmijat](https://forums.suse.com/u/predmijat)\
**Post date:** [February 1, 2017, 8:11am UTC](https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370/3 "2017-02-01T08:11:27Z")

</div>

Ok, that’s fine, but I’m having trouble finding the docs about updating `docker-compose.yml` in any way, not just via UI…would you mind providing the link?

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [February 1, 2017, 9:51am UTC](https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370/4 "2017-02-01T09:51:47Z")

</div>

[http://docs.rancher.com/rancher/v1.3/en/cattle/rancher-compose/](http://docs.rancher.com/rancher/v1.3/en/cattle/rancher-compose/)

Download links are in the page footer (“Download CLI”)

---

<div class="post-metadata">

**Author:** ![predmijat](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/predmijat/32/2091_2.png) [@predmijat](https://forums.suse.com/u/predmijat)\
**Post date:** [February 1, 2017, 3:22pm UTC](https://forums.suse.com/t/how-to-upgrade-docker-compose-yml-in-a-running-stack/5370/5 "2017-02-01T15:22:09Z")

</div>

Hm, there’s a link at the bottom of this page - [http://docs.rancher.com/rancher/v1.3/en/cattle/rancher-compose/commands/](http://docs.rancher.com/rancher/v1.3/en/cattle/rancher-compose/commands/) - about upgrading, but it’s 404 - [http://docs.rancher.com/rancher/v1.3/en/cattle/rancher-compose/upgrading/](http://docs.rancher.com/rancher/v1.3/en/cattle/rancher-compose/upgrading/)

From what I see in the docs, I’d do something like `rancher-compose up -d --upgrade`, right? That would upgrade only those services for which I’ve changed stuff (version or whatever)?