-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
connection plugin does not work with rootless containers #29
Comments
@tyll it should work. The problem is here:
For some reason you can't pause container. It reminds me problem containers/podman#4813 which was solved in ansible/ansible#66583. But seems like didn't work in your case, error message is different. Can you try please such a file? http://paste.openstack.org/show/793035/ Copy it to |
Great, thank you. This fixes it for me. There are now only warnings related to the python interpreter:
Let me know if you need more info. |
@tyll warning is fine. Glad it helped, will prepare a patch then. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
podman run --rm -it centos:8
ansible -vvi a935777de543, -c podman -m setup all
Describe the results you received:
Failed to mount container a935777de543: b'Error: cannot mount using driver overlay in rootless mode'
[WARNING]: Unhandled error in Python interpreter discovery for host a935777de543: Expecting value: line 1 column 1
(char 0)
a935777de543 | FAILED! => {
"msg": "Failed to set execute bit on remote files (rc: 1, err: chmod: cannot access '/root/.ansible/tmp/ansible-tmp-1588529245.4183488-80743-226755747598850/AnsiballZ_setup.py': No such file or directory\nError: non zero exit code: 1: OCI runtime error\n)"
}
Describe the results you expected:
Ansible should connect to the host.
If this is not supposed to work, the error message should be improved. Without extra verbosity it fails with the message about the temp file in
/root
. I guess the failure to mount the container should be a hard error instead of a warning.Additional information you deem important (e.g. issue happens only occasionally):
Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbok you run with ansible (e.g. content of
playbook.yaml
):Command line and output of ansible run with high verbosity:
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: