Open ehelms opened 7 years ago
I'm not sure if it did fail though? If I look at docker ps
some things do appear to be running:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b015f2a4c52c foreman-pulp-resource-manager:20170527012712 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes foreman_pulp-resource-manager_1
ac5c34744eca foreman-pulp-celerybeat:20170527012718 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes foreman_pulp-celerybeat_1
54300c33a659 foreman-pulp:20170527012700 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes 8080/tcp foreman_pulp_1
e8e21b82142e foreman-pulp-worker:20170527012706 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes foreman_pulp-worker_1
66627c6d8fee foreman-foreman-proxy:20170527012239 "/usr/bin/start-forem" 49 minutes ago Up 49 minutes 8080/tcp foreman_foreman-proxy_1
b7c1aebadb4c centos/mongodb-26-centos7:latest "container-entrypoint" 49 minutes ago Up 49 minutes 27017/tcp foreman_mongodb_1
c77bdac68bb3 ansible/postgresql:latest "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes 5432/tcp foreman_postgres_1
66105c853d0d foreman-foreman:20170527012136 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes 0.0.0.0:8080->8080/tcp foreman_foreman_1
84d21ee78a9d foreman-foreman-tasks:20170527012148 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes foreman_foreman-tasks_1
d53c40f61932 foreman-qpid:20170527012532 "/usr/bin/startup.sh" 49 minutes ago Up 49 minutes 5672/tcp foreman_qpid_1
35bad9d7f524 foreman-candlepin:20170527012454 "/usr/bin/entrypoint." 49 minutes ago Up 49 minutes 8080/tcp foreman_candlepin_1
a9521850b243 puppet/puppetserver:latest "dumb-init /docker-en" 49 minutes ago Up 49 minutes 8140/tcp foreman_puppet_1
Here is some output from running with --debug
since I hit this on two separate projects and I have no idea why they don't run:
TASK [docker_service] **********************************************************
task path: /home/ehelms/workspace/downstream/satellite-build/ansible-deployment/playbook.yml:3
Tuesday 30 May 2017 13:58:32 +0000 (0:00:00.040) 0:00:00.040 ***********
Using module_utils file /usr/lib/python2.7/site-packages/ansible/module_utils/basic.py
Using module_utils file /usr/lib/python2.7/site-packages/ansible/module_utils/docker_common.py
Using module_utils file /usr/lib/python2.7/site-packages/ansible/module_utils/_text.py
Using module_utils file /usr/lib/python2.7/site-packages/ansible/module_utils/pycompat24.py
Using module_utils file /usr/lib/python2.7/site-packages/ansible/module_utils/six/__init__.py
Using module_utils file /usr/lib/python2.7/site-packages/ansible/module_utils/six/_six.py
Using module file /usr/lib/python2.7/site-packages/ansible/modules/cloud/docker/docker_service.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: root
<127.0.0.1> EXEC /bin/sh -c 'echo ~ && sleep 0'
<127.0.0.1> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466 `" && echo ansible-tmp-1496152712.19-192579723797466="` echo /root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466 `" ) && sleep 0'
<127.0.0.1> PUT /tmp/tmp2HRTZz TO /root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466/docker_service.py
<127.0.0.1> EXEC /bin/sh -c 'chmod u+x /root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466/ /root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466/docker_service.py && sleep 0'
<127.0.0.1> EXEC /bin/sh -c '/usr/bin/python /root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466/docker_service.py; rm -rf "/root/.ansible/tmp/ansible-tmp-1496152712.19-192579723797466/" > /dev/null 2>&1 && sleep 0'
I think this may be an issue with the docker_service module, and perhaps related to ansible isssue #20480. Need to investigate further.
ISSUE TYPE
container.yml
OS / ENVIRONMENT
SUMMARY
Attempting to run
ansible-container run
to spin up deployment stack locally and I get an error. The error is not clear as to what the problem is however so that I can take steps to resolve the issue. I also tried running therun
command with--debug
but the output so verbose that I was unable to decipher what might be the issue.