# How to redeploy after image push

**URL:** <https://forums.suse.com/t/how-to-redeploy-after-image-push/1273>\
**Category:** Rancher 1.x\
**Created:** [December 16, 2015, 9:52pm UTC](https://forums.suse.com/t/how-to-redeploy-after-image-push/1273 "2015-12-16T21:52:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hannes\_brt](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/hannes_brt/32/334_2.png) [@hannes\_brt](https://forums.suse.com/u/hannes_brt)\
**Post date:** [December 16, 2015, 9:52pm UTC](https://forums.suse.com/t/how-to-redeploy-after-image-push/1273/1 "2015-12-16T21:52:01Z")

</div>

What is the preferred way to deploy an application after new images have been pushed?

When I do `rancher-compose pull; rancher-compose up --upgrade` it doesn’t seem to pick up the new images. It seems I need to run `rancher-compose rm --force`. Is that correct?

It would also be great if the Rancher UI could display the image hash such that it would be easier to tell which version of the image is running.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [December 16, 2015, 10:26pm UTC](https://forums.suse.com/t/how-to-redeploy-after-image-push/1273/2 "2015-12-16T22:26:03Z")

</div>

You could do a `rancher-compose --upgrade --pull` and keep the service the same in your docker-compose.yml.

[http://docs.rancher.com/rancher/rancher-compose/upgrading/#in-service-upgrade](http://docs.rancher.com/rancher/rancher-compose/upgrading/#in-service-upgrade)

Alternatively, you could just add the label `io.rancher.container.pull_image=always` and just do a `rancher-compose --upgrade`

[http://docs.rancher.com/rancher/labels/](http://docs.rancher.com/rancher/labels/)