"Getting started" cannot be completed

[jakabk]

Issue Type

• Bug report

Molecule and Ansible details

ansible 2.10.2
  config file = /home/jakabk/.ansible.cfg
  configured module search path = ['/home/jakabk/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/jakabk/.virtualenvs/ansible-roles/lib/python3.8/site-packages/ansible
  executable location = /home/jakabk/.virtualenvs/ansible-roles/bin/ansible
  python version = 3.8.1 (default, Jan 17 2020, 13:39:59) [GCC 8.3.0]
molecule 3.1.5
    ansible:2.10.2 python:3.8
    delegated:3.1.5 from molecule
    docker:0.2.4 from molecule_docker

Molecule installation method (one of):

• pip

Ansible installation method (one of):

• pip

Detail any linters or test runners used:

Desired Behavior

Getting Started Guide should work out of box.
It can be achieved by extending the "Getting Started Guide" with this

In order to complete this guide by hand, you will need initialize the role with docker driver
molecule init role my-new-role --driver-name docker

Actual Behaviour

If you init role with molecule init role my-new-role and follow the description you'll get:

jakabk@ansible:~$ molecule create
--> Test matrix
    
└── default
    ├── dependency
    ├── create
    └── prepare
    
--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'create'
    
    PLAY [Create] ******************************************************************
    
    TASK [Populate instance config dict] *******************************************
    skipping: [localhost]
    
    TASK [Convert instance config dict to a list] **********************************
    skipping: [localhost]
    
    TASK [Dump instance config] ****************************************************
    skipping: [localhost]
    
    PLAY RECAP *********************************************************************
    localhost                  : ok=0    changed=0    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0
    
--> Scenario: 'default'
--> Action: 'prepare'
Skipping, prepare playbook not configured

jakabk@ansible:~$ molecule list
Status(instance_name='instance', driver_name='delegated', provisioner_name='ansible', scenario_name='default', created='true', converged='false')
                ╷             ╷                  ╷               ╷         ╷            
  Instance Name │ Driver Name │ Provisioner Name │ Scenario Name │ Created │ Converged  
╶───────────────┼─────────────┼──────────────────┼───────────────┼─────────┼───────────╴
  instance      │ delegated   │ ansible          │ default       │ true    │ false

jakabk@ansible:~$ molecule converge
--> Test matrix
    
└── default
    ├── dependency
    ├── create
    ├── prepare
    └── converge
    
--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'create'
Skipping, instances already created.
--> Scenario: 'default'
--> Action: 'prepare'
Skipping, prepare playbook not configured.
--> Scenario: 'default'
--> Action: 'converge'
    
    PLAY [Converge] ****************************************************************
    
    TASK [Gathering Facts] *********************************************************
fatal: [instance]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname instance: No address associated with hostname", "unreachable": true}
    
    PLAY RECAP *********************************************************************
    instance                   : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0
    
ERROR: 

As a just-started-to-learn-molecule person, it has cost me 1.5 hours to get to work, and it was very annoying.

[ctorgalson]

Been using molecule for several years, but I can't get it to work at all in any new project now. I'm always seeing this same error on converge. Adding --driver-name docker to the init command makes no difference as far as I can tell.

[apatard]

With the --driver-name docker option, the converge stet of this doc is working here. Did you check that you have the molecule-docker driver installed and that the molecule.yml is correctly using docker and not delegated ?

[D1Ck3n]

i also cannot use molecule:

TASK [Gathering Facts] *********************************************************
fatal: [instance]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~/.ansible/tmp `\"&& mkdir ~/.ansible/tmp/ansible-tmp-1604937953.8861039-21879-212408116213348 && echo ansible-tmp-1604937953.8861039-21879-212408116213348=\"` echo ~/.ansible/tmp/ansible-tmp-1604937953.8861039-21879-212408116213348 `\" ), exited with result 1", "unreachable": true}

[staticdev]

@D1Ck3n did you find any solution for this error?

[kganchev]

@D1Ck3n @staticdev did you guys find any workaround to the temporary directory issue? It only happens to me when I try to use debian:testing or debian:buster docker images. It is all fine with ubuntu and centos images.

[decentral1se]

Yeah the docs needs a major overhaul but there is just no hands around to make that happen.

[decentral1se]

This should maybe a docs ticket on the issues list or @jakabk?

[jakabk]

Perhaps @decentral1se. I've opened it as an issue, and it was transformed into a discussion.

[pawsuch]

I had a similar issue with my molecule test @jakabk. I my case when I ran molecule converge prepare the docker container was created and I was able to actually start testing. The docs should be definitely updated.