Switching to pip3 and other modifications for AWX vagrant provisioner

oraclebase / vagrant

Vagrant Builds

https://oracle-base.com/

GNU General Public License v3.0

194 stars 169 forks source link

Switching to pip3 and other modifications for AWX vagrant provisioner #13

Closed ghost closed 3 years ago

ghost commented 4 years ago

I think these changes address some issues with the original code, as I tried using your scripts with a fresh AWX deployment and encountered Python/SELINUX errors during the playbook execution.

Recommended changes were using pip3 with the --user flag versus root/system-wide installations, setting vagrant into the docker group, and running the installation playbook under the vagrant user (opposed to root).

(Fixed a mistaken username in my prior pull request -- resubmitted)

ghost commented 4 years ago

Also -- if you go to test this, you might encounter a never-ending migration process at first startup.

There is an open issue for a similar complaint, and following the suggestion geerlingguy posted, it finishes migrations and starts up a fresh AWX instance. Reference: https://github.com/ansible/awx/issues/8387#issuecomment-724873700

oraclebase commented 3 years ago

I don't agree with some of the changes, so I'm going to close this pull request. I've updated the build to include some things though.

Installed the python3-pip and libselinux-python3 packages, as instructed by the build failure.
Switch pip calls to pip3.
I also cleaned up some of the old repository management, that was no longer necessary with the new "oraclebase/oracle-8" box.

Thanks for pointing out the failure. I'm not rebuilding these boxes all the time, so it can take a while for me to notice a new failure caused by a new version of AWX.