-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run ansible-runner with EEs #1406
Comments
I had a colleague try on Linux and they reproduced the error as well, so it's not Mac specific - I'll update the OP. |
You may need to also execute runner with Depending on the container runtime, executing user, and the configuration of the EE, running as the default user may produce an unusable container. |
Hey @sivel thanks for the tip, I tried adding that to the command from the description and see the same failure as before:
|
When running containerized, the (cwd) dir structure should look like:
So you need a |
fwiw, the directory layout is documented at https://ansible.readthedocs.io/projects/runner/en/latest/intro/#inputdir |
Thanks that got past the |
Ah, the |
I see similar as @agrare sees...it succeeds, but if I pass
|
The |
Closing this as it seems the initial problem was resolved by using the correct project structure. Thanks @sivel. |
I'm hitting a problem trying to run ansible-runner with a very simple EE / playbook. I'm using ansible-runner 2.4.0 on a MacOS M1 with podman-desktop. I also had @agrare try on Linux with ansible-runner 2.4.0, and he got the same issue
Running
$ ansible-runner run --process-isolation --container-image ghcr.io/ansible-community/community-ee-base:latest --playbook test_localhost.yml . --debug -vvvvv
where test_localhost.yml is
I get the following
I noticed that my job_events directory that was generated has files with a numeric prefix, and the code is not looking for that. For example, I see
but the error says it's looking for
The text was updated successfully, but these errors were encountered: