Molecule: FAILED - RETRYING: Build an Ansible compatible image

Created on 17 Dec 2019 · 1Comment · Source: ansible-community/molecule

Bug report

Molecule and Ansible details

ansible 2.9.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/joshua/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.15+ (default, Oct  7 2019, 17:39:04) [GCC 7.4.0]
molecule, version 2.22

Molecule installation method (one of):

Ansible installation method (one of):

OS package

Detail any linters or test runners used:

Desired Behavior

When I run the sudo molecule --debug test the test should be run successfully but it was giving the below error

System information

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:    18.04
Codename:   bionic

Actual Behaviour

When the run the sudo molecule --debug test I m getting the below error

 FAILED - RETRYING: Build an Ansible compatible image (new) (3 retries left).Result was: {
        "attempts": 1, 
        "changed": false, 
        "invocation": {
            "module_args": {
                "api_version": "auto", 
                "archive_path": null, 
                "build": {
                    "dockerfile": "/home/joshua/.cache/molecule/joshua.example/default/Dockerfile_centos_7", 
                    "path": "/home/joshua/.cache/molecule/joshua.example/default", 
                    "pull": true
                }, 
                "buildargs": null, 
                "ca_cert": null, 
                "client_cert": null, 
                "client_key": null, 
                "container_limits": null, 
                "debug": false, 
                "docker_host": "unix://var/run/docker.sock", 
                "dockerfile": null, 
                "force": null, 
                "force_absent": false, 
                "force_source": true, 
                "force_tag": false, 
                "http_timeout": null, 
                "load_path": null, 
                "name": "molecule_local/centos:7", 
                "nocache": false, 
                "path": null, 
                "pull": null, 
                "push": false, 
                "repository": null, 
                "rm": true, 
                "source": "build", 
                "ssl_version": null, 
                "state": "present", 
                "tag": "latest", 
                "timeout": 60, 
                "tls": false, 
                "tls_hostname": "localhost", 
                "tls_verify": false, 
                "use_tls": null, 
                "validate_certs": false
            }
        }, 
        "msg": "An unexpected docker error occurred: Credentials store error: StoreError('Credentials store docker-credential-secretservice exited with \"Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached\".',)", 
        "retries": 4
    }

But I was able to login into the docker hub successfully using docker login and the docker configuration was

{
    "auths": {
        "https://index.docker.io/v1/": {}
    },
    "HttpHeaders": {
        "User-Agent": "Docker-Client/19.03.4 (linux)"
    },
    "credsStore": "secretservice"
}

bug

Source