Last active
June 17, 2021 04:41
-
-
Save deekayen/af33872cf64faa28e95ba593582abd5e to your computer and use it in GitHub Desktop.
Upgrade Ansible AWX containers
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
docker stop awx_task | |
docker rm awx_task | |
docker rmi ansible/awx_task:latest | |
docker stop awx_web | |
docker rm awx_web | |
docker rmi ansible/awx_web:latest | |
git pull | |
cd installer | |
# Review inventory | |
ansible-playbook -i inventory install.yml |
https://github.com/ansible/awx/blob/devel/DATA_MIGRATION.md
Here's an article you can read on it as well. It has some steps you can take to migrate some of the data. But its not as straight forward as deleting the docker container and running the installer playbook to upgrade.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably to a certain degree. It’s a known problem. If they make changes to the database there’s no good way to migrate to the next version with docker. It makes sense since docker images just run the application where an installer would get you the upgrades to your database as needed. You can mitigate some of it by exporting your templates through the UI but things like logins, AD integration, project files doesn’t carry over. It gets worse when you have to build your image like I have to.
Unless somethings changed that I’m not aware of, but it’s basically why I don’t upgrade regularly with it. In fact I only ever upgraded once because once was enough! I just happened to be in an upgrade path that had a database change and it hosed me. Luckily I was still in the POC phase of using it so it didn’t hurt too bad.
Anyways, it’s just something to keep in mind when doing it. Just have to be sure there’s no database change in your upgrade path.