Pipelining causes Error: cannot run command "podman mount" in rootless mode

[kees-closed]

Issue Type

• Bug report

Molecule and Ansible details

$ ansible --version && molecule --version
ansible 2.9.18
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/kjong/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.9/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.9.2 (default, Feb 20 2021, 00:00:00) [GCC 10.2.1 20201125 (Red Hat 10.2.1-9)]
molecule 3.2.3 using python 3.9 
    ansible:2.9.18
    delegated:3.2.3 from molecule
    docker:0.2.4 from molecule_docker
    podman:0.3.0 from molecule_podman

Molecule installation method (one of):

• OS package

Ansible installation method (one of):

• OS package

Detail any linters or test runners used:

Desired Behavior

When I start Molecule with Podman as container driver, I get the error: cannot run command "podman mount" in rootless mode, must execute podman unshare first'

However, after figuring out what could cause this, I found out that pipelining in the ssh_connection section of my ansible.cfg is to triggering this.

This is my provisioner stanza of my molecule.yml:

provisioner:
  name: ansible
  env:
    ANSIBLE_CONFIG: ansible.cfg
    ANSIBLE_ROLES_PATH: ../../roles/
    ANSIBLE_LOOKUP_PLUGINS: ../../lookup_plugins/
    ANSIBLE_VAULT_PASSWORD_FILE: vault-pass
    MOLECULE_NO_LOG: true
  inventory:
    links:
      group_vars: ../../group_vars/
      host_vars: ../../host_vars/

With this I include my ansible.cfg, where the pipelining is set to true. When I set this to false it works again.

Is pipelining interfering with the inner workings of molecule somehow?

Actual Behaviour

When I do a molecule converge, I get the following error when pipelining is enabled:

Failed to mount container rp1: b'Error: cannot run command "podman mount" in rootless mode, must execute `podman unshare` first'         
<rp1> RUN [b'podman', b'exec', b'rp1', b'/bin/sh', b'-c', b'sudo -H -S  -p "[sudo via ansible, key=jhiskphfictutojpcopqgiygccunnwrp] password:" -u root /bin/sh -c \'echo BECOME-SUCCESS-jhiskphfictutojpcopqgiygccunnwrp ; /usr/bin/python3\' && sleep 0']                       
fatal: [rp4]: FAILED! => {                                                                                                               
    "ansible_facts": {},                                                                                                                 
    "changed": false,                                                                                                                    
    "failed_modules": {                                             
        "setup": {        
            "failed": true,                                         
            "module_stderr": "",              
            "module_stdout": "",       
            "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",                                                              
            "rc": 0                                                                                                                      
        }                                                                                                                                
    }                           
}                                                                                                                                        
                                                                    
MSG:                                   
                                                                                                                                         
The following modules failed to execute: setup

Summary

So this basically leaves me with a few questions.

This may be fixed by simply override the pipelining setting in ansible.cfg. But the documentation is not clear about how to do this.

It seems it can be done like this:

provisioner:
  name: ansible
  config_options:
    ssh_connection:
      pipelining: false

But also like this?:
ansible:

  config_file: /path/to/your/ansible.cfg
  ansiblecfg_ssh_connection:
    pipelining: True

However, the only thing that does work is this, when I don't set the ANSIBLE_CONFIG environment variable:

provisioner:
  name: ansible
  config_options:
    ssh_connection:
      pipelining: false

When I set pipelining to true in the above example, then the error shows up again.

So, I would like to know the following:

1. What's the current and working way to include an ansible.cfg config and override one or more options? Mainly the pipelining option.
2. The documentation seems to be all over the place. There is this one and this one. Both contain different examples.
3. So what would be the goto place to get an overview of all config options and examples? Because some examples are not working, while they are documented. Some examples are the above pipelining settings. But there are more things in that same context and config scope.

[kees-closed]

Any feedback on this? :)

[will-maclean]

Did anyone end up finding a resolution for this?

[kees-closed]

Haven't used it in a while. Disabling pipelining was a solution back then.