thomvaill / tads-boilerplate

Terraform + Ansible + Docker Swarm boilerplate = DevOps on :fire::fire::fire: | Infrastructure as Code

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Example Proviosion playbook failed

mieel opened this issue · comments

Describe the bug
Im up to this command from your example
> ./tads ansible-playbook localhost provision

Tasks are executing fine up to this one:

PLAY [docker:&dockerswarm_manager] *************************************************************************************************************************************

TASK [Gathering Facts] *************************************************************************************************************************************************ok: [127.0.0.1]

TASK [load docker info as facts] ***************************************************************************************************************************************An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: Value of unknown type: <class 'urllib3.exceptions.ProtocolError'>, ('Connection aborted.', error(2, 'No such file or directory'))
fatal: [127.0.0.1]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n  File \"/root/.ansible/tmp/ansible-tmp-1575456373.86-208554238811029/AnsiballZ_docker_info_facts\", line 102, in <module>\n
 _ansiballz_main()\n  File \"/root/.ansible/tmp/ansible-tmp-1575456373.86-208554238811029/AnsiballZ_docker_info_facts\", line 94, in _ansiballz_main\n
invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n
File \"/root/.ansible/tmp/ansible-tmp-1575456373.86-208554238811029/AnsiballZ_docker_info_facts\", line 40, in invoke_module\n    runpy.run_module(mod_name='ansible.modules.docker_info_facts', init_globals=None, run_name='__main__', alter_sys=True)\n  File \"/usr/lib/python2.7/runpy.py\", line 188, in run_module\n    fname, loader, pkg_name)\n  File \"/usr/lib/python2.7/runpy.py\", line 82, in _run_module_code\n    mod_name, mod_fname, mod_loader, pkg_name)\n
File \"/usr/lib/python2.7/runpy.py\", line 72, in _run_code\n    exec code in run_globals\n  File \"/tmp/ansible_docker_info_facts_payload_5ZDtsE/ansible_docker_info_facts_payload.zip/ansible/modules/docker_info_facts.py\", line 78, in <module>\n
File \"/tmp/ansible_docker_info_facts_payload_5ZDtsE/ansible_docker_info_facts_payload.zip/ansible/modules/docker_info_facts.py\", line 69, in main\n  File \"/tmp/ansible_docker_info_facts_payload_5ZDtsE/ansible_docker_info_facts_payload.zip/ansible/module_utils/basic.py\", line 2093, in fail_json\n  File \"/tmp/ansible_docker_info_facts_payload_5ZDtsE/ansible_docker_info_facts_payload.zip/ansible/module_utils/basic.py\", line 2065, in _return_formatted\n  File \"/tmp/ansible_docker_info_facts_payload_5ZDtsE/ansible_docker_info_facts_payload.zip/ansible/module_utils/basic.py\", line 418, in remove_values\n
File \"/tmp/ansible_docker_info_facts_payload_5ZDtsE/ansible_docker_info_facts_payload.zip/ansible/module_utils/basic.py\", line 401, in _remove_values_conditions\nTypeError: Value of unknown type: <class 'urllib3.exceptions.ProtocolError'>, ('Connection aborted.', error(2, 'No such file or directory'))\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

Any Idea how where to look at?

To Reproduce
Steps to reproduce the behavior:
> ./tads ansible-playbook localhost provision

Expected behavior
A clear and concise description of what you expected to happen.

Environment (please complete the following information):

  • OS/distro: Latest Ubuntu docker image, on windows Docker Desktop

Additional context
Add any other context about the problem here.

Hi @mieel,
I suppose this error is specific to your Windows Docker Desktop environment.

I tried to reproduce it but unfortunately, I only have a Virtualbox Windows VM, and Docker Desktop cannot be executed inside it because of Hyper-V :(

As soon as I have an available bare metal Windows machine, I will try to debug it.
In the meantime, if someone is able to debug this error, it would be great!

commented

@mieel - would you check if the updates in #13 fix this as well?