# Stack upgrade with compose files

**URL:** <https://forums.suse.com/t/stack-upgrade-with-compose-files/6563>\
**Category:** Rancher 1.x\
**Created:** [June 6, 2017, 11:10am UTC](https://forums.suse.com/t/stack-upgrade-with-compose-files/6563 "2017-06-06T11:10:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Badger](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@Badger](https://forums.suse.com/u/Badger)\
**Post date:** [June 6, 2017, 11:10am UTC](https://forums.suse.com/t/stack-upgrade-with-compose-files/6563/1 "2017-06-06T11:10:58Z")

</div>

Hi,

Using Rancher v1.6.0.

Is there a plan to enable changes in rancher-compose.yml file to actually trigger the upgrade?  
If we choose to change the hostname or port values, can this be done without removing the stack and creating a new one?

Also, the label “io.rancher.container.pull\_image: always” doesn’t really pull the :latest image from the repo, nor does the --pull switch work. Only the --force-upgrade actually works so I’m wondering if we’re doing something wrong or if the upgrade only works if you actually change the image name.