On your kubernetes box? No there won’t be. You are looking at containers. On the box where you authored the image run docker image
Docker image ls
I’ve just deployed a new custom EE to my AWX setup and it’s working. So my LinkedIn instructions are working. I’ve added a troubleshooting section to the end of the blog, in case it might be useful for you - https://www.linkedin.com/pulse/creating-custom-ee-awx-phil-griffiths/
Hi Phil,
I found this issue…
and found this:
Separately, I had similar issues as reported in 9917 but was able to eventually get a custom EE container builtt and working (to include Galaxy collections) by using the workarounds mentioned there. I needed to use your suggested --build-arg ANSIBLE_RUNNER_IMAGE=[quay.io/ansible/awx-ee:0.1.1](http://quay.io/ansible/awx-ee:0.1.1)
When I used this The playbook ran as expected. The playbook did error but that is expected and comes under standard bug fixing.
Thank you for taking the time to help me. It is most appreciated.
Spoke too soon , it looks like the image built, using those args but no pwsh binary got installed in that image . When I use that image as the parent now it says it can’t find kubernetes.core collection.
Back to square one…I’ll send a new message…
The steps on the linkedin page worked for me - thanks!