# AWX Upgrade UI/TASK to latest version

**URL:** <https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [December 19, 2017, 3:56pm UTC](https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331 "2017-12-19T15:56:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Devin\_Acosta](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@Devin\_Acosta](https://forum.ansible.com/u/Devin_Acosta)\
**Post date:** [December 19, 2017, 3:56pm UTC](https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331/1 "2017-12-19T15:56:36Z")

</div>

I am running AWX running DockerCE community version on a CentOS 7 Virtual Machine. I see there are newer images of the Web UI and Task images and want to know what is the proper way up upgrade those 2 containers without loosing my data?

---

<div class="post-metadata">

**Author:** ![jmitchel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jmitchel/32/10148_2.png) [@jmitchel](https://forum.ansible.com/u/jmitchel)\
**Post date:** [December 19, 2017, 7:23pm UTC](https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331/2 "2017-12-19T19:23:41Z")

</div>

There was just a large merge of work into the AWX codebase. As such there will most likely be some backwards incompatible changes that make upgrading difficult. This is mentioned in a [thread](https://groups.google.com/forum/#!topic/awx-project/PQLxKl5Rj9) on the release of 1.0.2

---

<div class="post-metadata">

**Author:** ![Tobias\_Wolf](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@Tobias\_Wolf](https://forum.ansible.com/u/Tobias_Wolf)\
**Post date:** [December 28, 2017, 8:57pm UTC](https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331/3 "2017-12-28T20:57:08Z")

</div>

Do you foresee to do this on a regular basis in this project?

What will Tower users do? There must be an upgrade path?

---

<div class="post-metadata">

**Author:** ![Andrew\_Crisp](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@Andrew\_Crisp](https://forum.ansible.com/u/Andrew_Crisp)\
**Post date:** [January 2, 2018, 2:40pm UTC](https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331/4 "2018-01-02T14:40:01Z")

</div>

Hi John - can we get some clarity regarding upgrading and problems ? My thoughts were / belief that the configuration is held in Postgres dB ? Therefore we should be able to blow away the web and task docker containers at will and redeploy ? If we have the inventory / or enter previous values into new inventory ie passwords. Are you therefore suggesting it is changes to the dB schema that will cause an upgrade to fail ?

Andy

---

<div class="post-metadata">

**Author:** ![Greg\_DeKoenigsberg](https://avatars.discourse-cdn.com/v4/letter/g/c68b51/32.png) [@Greg\_DeKoenigsberg](https://forum.ansible.com/u/Greg_DeKoenigsberg)\
**Post date:** [January 2, 2018, 8:23pm UTC](https://forum.ansible.com/t/awx-upgrade-ui-task-to-latest-version/26331/5 "2018-01-02T20:23:50Z")

</div>

A reminder: the primary purpose of Tower is stability, and the primary  
purpose of AWX is to move fast, even at the risk of occasionally  
breaking things.

Tower upgrades are different because we have much stronger assurances  
about customer environments, and because we're on the hook to fix  
those issues if they go wrong. Upgrades for AWX are not a priority,  
and we don't want to make promises about upgradability that we won't  
be able to keep.

One possible workaround for AWX users is to export data from the old  
AWX instance using the Tower API/CLI, and then import that data to the  
new AWX instance.