Thank you again, Phil, but I'm back to the same old square 1. I did the full Ansible document on the Docker host server and at the end, it would not accept my venv folder as a valid venv path choice. I was hopeful the containers would pick up the venv from the host, but that does not happen. And besides, /var/lib/awx does not exist on the host. I created my venv smoothly on the host box, down to the last and happy step, but it doesn't flow into the containers (which is good, because I distrust magic anyway. Mayhap there's a config document in which I'm supposed to tell AWX which host files to pick up, but that sounds sketchy.)
So, it appears I need to add the venv on the Task and Web servers, but I cannot find any way to install the gcc there. CentOS8 won't pull it from the yum repos and I cannot "make" the compiler from tar because doing so needs the compiler. Besides, if I succeeded at this build, would it all not just disappear in the next image refresh, and maybe even in the next restart?
So, my hope again is that I can modify something to make that pickup happen. Looking in the install path I found:
vi <installPath>/awx/installer/inventory
In it I modified:
# AWX custom virtual environment folder. Only usable for local install.
#custom_venv_dir=/opt/my-envs/
custom_venv_dir=<installPath>/ansible-envs
After making the change and restarting my task and web containers I still get:
{"CUSTOM_VENV_PATHS":["<installPath>/ansible-envs/ is not a valid path choice."]}
Rereading, but I think I'm snookered. None of this is in my sweet spot. I write playbooks that maintain load balancers. I've never issued a yum command outside cut and paste in my life, but if I'm going to automate InfoBlox I've got to build the tool. I'm probably missing something dumb, but I'm not seeing it yet.
Kevin