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
Running ansible-navigator from a non-root account causes error #1534
Comments
UpdateI did some additional testing today and I think this is an issue with podman itself and not necessarily ansible-navigator. Podman Version
OS Version
STEPS TO REPRODUCE
Expected Results
Actual ResultsWhen running after
|
One more additional thing I will add. When you login directly over SSH as the unprivileged user, it does map the XDG_RUNTIME_DIR correctly and the container will pull or run properly.
When doing a
When doing a
When doing a
If you attempt to map the XDG_RUNTIME_DIR manually, it still gives a similar error
|
Final update and I will take a break from troubleshooting this. It appears to me that it is potentially a problem with the su command and how it interacts with environment variables related to podman. I just did a test where I have 2 unprivileged users (bob and sally) and I use the When doing a
When doing a
|
It appears the podman team is aware of this bug and looking for a better way to warn users of the potential pitfall of using I personally would like to understand why there can't be a permanent fix for this issue or what is preventing |
ISSUE TYPE
SUMMARY
There is an issue with ansible-navigator or possibly podman when using the
su
orsu -
switching from the root user to an unprivileged user and attempting to run theansible-navigator
command.ANSIBLE-NAVIGATOR VERSION
CONFIGURATION
LOG FILE
https://gist.github.com/noelmiller/410131a2ffc51e756bef00dcd8e9af0f
STEPS TO REPRODUCE
ssh root@control-node
su user
su - user
su --login user
EXPECTED RESULTS
Expect the interactive ansible-navigator tui to appear, but instead I get the error below.
ACTUAL RESULTS
ADDITIONAL INFORMATION
This could be an issue with podman itself, I did find another resolved github issue talking about switching user from root to unprivileged user here: containers/podman#8052
The text was updated successfully, but these errors were encountered: