# AWX docker container upgrade

**URL:** <https://forum.ansible.com/t/awx-docker-container-upgrade/26291>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [December 14, 2017, 11:54am UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291 "2017-12-14T11:54:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Choon\_Ming\_Goh](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@Choon\_Ming\_Goh](https://forum.ansible.com/u/Choon_Ming_Goh)\
**Post date:** [December 14, 2017, 11:54am UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291/1 "2017-12-14T11:54:54Z")

</div>

Hi,

I’m currently running AWX 1.0.1 on Amazon ECS with external postgresql on RDS. It is working fine but now I want to upgrade it to 1.0.2. There are indications there I should just update the ECS definitions to use the AWX image 1.0.2. I did that and then when I try to open up AWX page, it would just be stuck on the page /migration\_notran for a long time.

Is there a way to resolve this? If I revert back to the 1.0.1 image, I would be able to login again but I will have errors such as

`  
Failed updating job undefined with variables. POST returned: 400 null  
value in column “setting” violates not-null constraint  
DETAIL: Failing row contains (3160, create, 2017-12-14  
11:54:27.846241+00, {“project”: “ansible:feature/SYST-639-6”,  
“use\_fact\_cache”: fals…, , job, , 1, null).

`

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [December 14, 2017, 1:37pm UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291/2 "2017-12-14T13:37:15Z")

</div>

You’ll want to see my announcement message from yesterday… upgrading from 1.0.1 to 1.0.2 beyond 1.0.2.0 might be difficult/impossible.

I’m working on getting a 1.0.2.0 image built and pushed to our registry but in the meantime you may want to build it locally and use that.

---

<div class="post-metadata">

**Author:** ![Choon\_Ming\_Goh](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@Choon\_Ming\_Goh](https://forum.ansible.com/u/Choon_Ming_Goh)\
**Post date:** [December 15, 2017, 9:24am UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291/3 "2017-12-15T09:24:38Z")

</div>

Thanks Matt. Would you have any ETA on that?

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [December 15, 2017, 2:58pm UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291/4 "2017-12-15T14:58:26Z")

</div>

should be up now

---

<div class="post-metadata">

**Author:** ![Choon\_Ming\_Goh](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@Choon\_Ming\_Goh](https://forum.ansible.com/u/Choon_Ming_Goh)\
**Post date:** [December 19, 2017, 10:34am UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291/5 "2017-12-19T10:34:26Z")

</div>

Hi Matt,

I’m running the container 1.0.2.0 and I’m getting the error below when I try to execute a template

`  
Failed updating job undefined with variables. POST returned: 400 null  
value in column “setting” violates not-null constraint  
DETAIL: Failing row contains (17379, create, 2017-12-19  
10:32:43.215291+00, {“project”: “ansible:feature/SYST-639-6”,  
“use\_fact\_cache”: fals…, , job, , 1, null).

`

---

<div class="post-metadata">

**Author:** ![Choon\_Ming\_Goh](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@Choon\_Ming\_Goh](https://forum.ansible.com/u/Choon_Ming_Goh)\
**Post date:** [December 19, 2017, 1:24pm UTC](https://forum.ansible.com/t/awx-docker-container-upgrade/26291/6 "2017-12-19T13:24:08Z")

</div>

Resolved by using the image 1.0.2.285 then 1.0.2