There’s a solved ansible-navigator issue #1448 regarding an error when running
ansible-navigator in that it reports “ERROR! Invalid callback for stdout specified: awx_display”.
I am seeing the same error using
head -4 env/settings --- process_isolation: true process_isolation_executable: podman container_image: quay.io/ansible/awx-ee $ ansible-runner run . -p demo.yml [WARNING]: Unable to parse /runner/inventory/hosts as an inventory source [WARNING]: No inventory was parsed, only implicit localhost is available [WARNING]: error in 'jsonfile' cache plugin while trying to create cache dir /runner/artifacts/7c4f751e-9bcf-4676-9d99-e581b7cc2738/fact_cache : b"[Errno 13] Permission denied: '/runner/artifacts/7c4f751e-9bcf-4676-9d99-e581b7cc2738/fact_cache'" [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all' ERROR! Invalid callback for stdout specified: awx_display
I think I’ve worked around it by building a custom EE with
options.user: '0', which is going to mean do everything as root, possibly/probably a pretty bad idea, but I wanted to at least once experience runner with isolation.
Could somebody who has a lot more container experience than myself (and I promise that’s not something hard to have) explain the ramifications of running a podman container with root privileges within said container?