You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2019. It is now read-only.
For docker_service the image in the playbook should have this format: image: docker-host:5000/ansible-container/ansible-container-web:v1
ACTUAL RESULTS
Currently the playbook has: image: http://docker-host:5000/ansible-container/ansible-container-web
Which causes these errors:
the protocol: Error starting project Repository name cannot contain a scheme (http://docker-host:5000/ansible-container/ansible-container-nodes)
the lack of tag: Error: image ansible-container/ansible-container-nodes:latest not found
Also notice the lack of the "v1" tagged image in the "destroy" process. Executing: ansible-playbook -i hosts docker-deploy/ansible-container.yml -t destroy
only removed ansible-container-web:latest and ansible-container-web:20170603180431, leaving ansible-container-web:v1 behind.
ISSUE TYPE
container.yml
Where testapp is a very basic django app which only displays a test page.
generated ansible-container.yml
SUMMARY
Running deploy with docker engine produces a playbook that contains three simple-to-fix errors.
STEPS TO REPRODUCE
EXPECTED RESULTS
For docker_service the image in the playbook should have this format:
image: docker-host:5000/ansible-container/ansible-container-web:v1
ACTUAL RESULTS
Currently the playbook has:
image: http://docker-host:5000/ansible-container/ansible-container-web
Which causes these errors:
Error starting project Repository name cannot contain a scheme (http://docker-host:5000/ansible-container/ansible-container-nodes)
Error: image ansible-container/ansible-container-nodes:latest not found
Also notice the lack of the "v1" tagged image in the "destroy" process. Executing:
ansible-playbook -i hosts docker-deploy/ansible-container.yml -t destroy
only removed ansible-container-web:latest and ansible-container-web:20170603180431, leaving ansible-container-web:v1 behind.
OS / ENVIRONMENT
The text was updated successfully, but these errors were encountered: