Molecule: Failure to discover local Docker images

Created on 11 Jul 2018  路  6Comments  路  Source: ansible-community/molecule

Issue Type

  • Bug report

Molecule and Ansible details

ansible --version
ansible 2.6.1
  config file = None
  configured module search path = [u'/Users/jpereira/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.14 (default, Mar 22 2018, 14:43:05) [GCC 4.2.1 Compatible 

molecule --version
molecule, version 2.16.0

Molecule installation method (one of):

  • pip

Ansible installation method (one of):

  • brew

Desired Behavior

Trying to run and ssh into a basic role created through molecule.

Actual Behaviour (Bug report only)

TASK [Discover local Docker images] ********************************************
    failed: [localhost] (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
    fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}

I receive this error when I input molecule converge into terminal

Most helpful comment

As a quick note for others who may bump into this, the error is hidden by the "censored" output. In my case, it was not the pull: false issue but the fact that I was missing the pipdocker or docker-py requirement for molecule.

This was a fresh install - so I was going from memory (bad me).

All 6 comments

I can't really help you based on the information provided. Please run molecule --debug and provide appropriate details.

You're not giving a lot of info of what you're doing specifically, but based on the title I think this might be a duplicate of #1234 . In summary: In the create.yml playbook, which is used to create an instance, the docker_image module is used. Setting pull: false here would perhaps solve the issue.

As a quick note for others who may bump into this, the error is hidden by the "censored" output. In my case, it was not the pull: false issue but the fact that I was missing the pipdocker or docker-py requirement for molecule.

This was a fresh install - so I was going from memory (bad me).

docker --version
Docker version 18.09.0, build 4d60db4
molecule --version
molecule, version 2.20.0
ansible --version
ansible 2.8.0a1
config file = /etc/ansible/ansible.cfg
configured module search path = ['/Users/user_name/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.7/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.7.3 (default, Mar 27 2019, 09:23:15) [Clang 10.0.1 (clang-1001.0.46.3)]

my molecule.yml has

dependency:
  name: galaxy
driver:
  name: docker
lint:
  name: yamllint
platforms:
  - name: instance
    image: centos:7
    pull: False
provisioner:
  name: ansible
  lint:
    name: ansible-lint
scenario:
  name: default
verifier:
  name: testinfra
  lint:
    name: flake8

Error i get

TASK [Discover local Docker images] ********************************************
    failed: [localhost] (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
    fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}

can someone help to resolve this issue
is there a way to override no_log:true ??

is there a way to override no_log:true ??

@vignajethkk, pass --debug to your molecule invocation :+1:

Ah, I see https://github.com/ansible/molecule/issues/1999#issuecomment-485467549 now, great!

pip install docker

Was this page helpful?
0 / 5 - 0 ratings