-
Notifications
You must be signed in to change notification settings - Fork 98
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
Version 3 builder images cannot be used with ansible-navigator #541
Comments
This one is the problem:
|
I need to dig deeper, but this is as far as I got so far, we call
I'll debug runner after a bit. |
Rootless podman assumes host UID == container UID0/GID0, but since we "can't" default the container to
I think option #3 is the most compatible choice for Navigator's typical host-agility needs as a dev tool. |
Any of that would need to be done by runner.... Navigator doesn't craft the command line. Will look at the runner code later tonight. |
this works fine for podman but not for docker
works fine for podman, until docker is installed, "OCI permission denied", appears to be the docker group membership So the last question is, should this be fixed in runner? or in navigator? It appears |
it appears userns was once in runner: ansible/ansible-runner#759 |
Apparently Docker also has a rootless mode (https://docs.docker.com/engine/security/rootless/), which will make this even more ... interesting :) |
I went ahead and merged the navigator PR and released version 3.3.1, the tests were passing and I had good success with it locally. I still find myself thinking container engine specific CLI requirements related to builder built execution environments might be better in runner, but I also understand touching runner can have a much bigger impact than navigator. |
Thanks @cidrblock I confirm that ansible-navigator 3.3.1 fixed the issue. |
Using a builder built image:
When used with navigator:
I suspect the issue here is the
Permission Denied
, runner cannot copy it'sawx_display
callback plugin into the artificat directory.The dir being mounted is 700:
and from within the ee it is inaccessable:
The full invocation of the ee is as follows:
The text was updated successfully, but these errors were encountered: