# Update docker image without changing tag

**URL:** <https://forums.suse.com/t/update-docker-image-without-changing-tag/465>\
**Category:** Rancher 1.x\
**Created:** [September 14, 2015, 10:23am UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465 "2015-09-14T10:23:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rewop](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@rewop](https://forums.suse.com/u/rewop)\
**Post date:** [September 14, 2015, 10:23am UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465/1 "2015-09-14T10:23:22Z")

</div>

What is the best way to update an image in rancher without having to use a different tag?

I am testing my application with an `alpha` tag. However when I push a new version of the same tag on the registry, and recreate the service in Rancher, the new image is not pulled.

I see from [1874](https://github.com/rancher/rancher/issues/1874) that the feature request has been made.

This is very useful for some of our development steps. What is your suggestion to handle this scenario at the current stage?

---

<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:** [September 22, 2015, 4:51pm UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465/2 "2015-09-22T16:51:39Z")

</div>

Currently, the only workaround would be to go directly to the hosts and pull the docker image. After the image has been pulled, the cleanest way would probably be to “upgrade” your service using rancher-compose, which would essentially launch all new containers using the same image (if you didn’t want to change the tag).

[http://docs.rancher.com/rancher/rancher-compose/upgrading/](http://docs.rancher.com/rancher/rancher-compose/upgrading/)

---

<div class="post-metadata">

**Author:** ![alex88](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/alex88/32/105_2.png) [@alex88](https://forums.suse.com/u/alex88)\
**Post date:** [September 23, 2015, 10:29am UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465/3 "2015-09-23T10:29:25Z")

</div>

Right now there is the new `rancher-compose pull` command, however it says the image cannot be found for private images, is that expected?

---

<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:** [September 23, 2015, 5:17pm UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465/4 "2015-09-23T17:17:51Z")

</div>

No, it’s expected to work. I’ve tagged your issue in Github as a bug and we will hope to fix it in the next release.

---

<div class="post-metadata">

**Author:** ![rm2016](https://avatars.discourse-cdn.com/v4/letter/r/49beb7/32.png) [@rm2016](https://forums.suse.com/u/rm2016)\
**Post date:** [March 4, 2016, 6:23pm UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465/5 "2016-03-04T18:23:06Z")

</div>

Has this been fixed, I would like to manually pull the new image when ready, since our stack launches every hour for 5 min then shut down. We currently have the image being pull every time it starts the instance but we are seeing bandwidth cost.

---

<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:** [March 4, 2016, 8:13pm UTC](https://forums.suse.com/t/update-docker-image-without-changing-tag/465/6 "2016-03-04T20:13:46Z")

</div>

It sounds like you are looking for:

[https://github.com/rancher/rancher/issues/1277](https://github.com/rancher/rancher/issues/1277)