Re: [ansible-project] Docker module error

Hello- Without all the info, this looks similar to something I ran into. Try: pip3 install docker This will install the docker Python module for the version of Python that Ansible is using (3.6.7). Better yet, have a task in your playbook install it prior to using the docker Ansible module.

[ansible-project] Docker module error

Hi, Please help to get this resolved, tried all most everything. Ansible Version: ansible 2.7.10 config file = /etc/ansible/ansible.cfg configured module search path = ['/home/stack/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location =

Re: [ansible-project] Docker module for `docker-compose run`?

http://docs.ansible.com/ansible/latest/docker_service_module.html On Mon, Jan 29, 2018 at 2:28 PM, Brandon Schlueter wrote: > In writing a playbook to bring up sentry according to its docs with > docker-compose, I ended up with a task list including: > > - name: run

[ansible-project] Docker module for `docker-compose run`?

In writing a playbook to bring up sentry according to its docs with docker-compose, I ended up with a task list including: - name: run database migrations command: docker-compose run --rm web upgrade --noinput chdir=/opt/sentry-onpremise - name: create initial user command: docker-compose run

[ansible-project] docker module requirements met, but ansible misses docker-py

Hello everybody, got 2 Servers with docker and ansible requirements to manipulate them. But at server B , ansible doent find docker-py allthough it is installed. The versions of the installed softwares differ, so i guess there is the problem. Server A(working): python2.7

[ansible-project] Docker module giving error after image is pulled

I have a role that runs nginx in a docker container using the official nginx image from docker hub. The docker task returns the following error after it pulls the image: "failed": true, "msg": "Unrecognized status from pull.", "status": "docker.io/library/nginx: this image was pulled from a

[ansible-project] docker module wont link port (but shell will)

Hi, im running this[1] playbook against a server in order to start a logstash container, but i cannot get it to link the required ports. This[2] is the full log of that run and nothing seems to be wrong, but when i do a `docker ps` i cannot see the ports[3]. If i run the corresponding docker

[ansible-project] Docker module choose random port if we didn't pass ports variable.

In 1.8.0 version, If I didn't pass ports variable, Docker module will not bind any port to the Docker Host. It worked correctly. However, In 1.9.0.1, Docker module choose a random ports, and bind to Docker Host. I think there is something wrong. Please correct me if I wrong. If I remove this

[ansible-project] Docker module state argument

Community, I'm using the docker module and the documentation appears to be wrong. I'm not sure where the right place is to bring this up. I'm running ansible version 1.8.2. Ansible Documentation: http://docs.ansible.com/docker_module.html http://docs.ansible.com/docker_module.html

Re: [ansible-project] Docker module state argument

I believe this was added to the latest docker module (devel) but the documentation was update w/o a 'version added'. -- Brian Coca -- You received this message because you are subscribed to the Google Groups Ansible Project group. To unsubscribe from this group and stop receiving emails from

[ansible-project] Docker module required arguments - should image always be mandatory?

Hi there. I'm fairly certain the docker module is working as designed, but I wanted to make sure before I create an issue on github. - name: stop docker container docker: name=myapp image=myappimage state=absent I was poking around the docker.py code, and it seems like it's

[ansible-project] Docker Module. Defining Ports

Hi, I'm trying to start Docker using the core module provided by Ansible and I'm running into issues defining ports forwarding. It is currently defined as: ports: 4:8185,40001:22,40002:61000 When the playbook runs, only port 22 gets exposed correctly. According to the output of docker

[ansible-project] Docker module not responding correctly to commands

Hi i hope not to a duplicate any post but I have a preety akward problem with the docker module to ansible. I have a services.yml file: --- services: - {service: articleadmin, tag: dev, add: env='DATACENTER_ID={{dc_id}}'} - {service: articlemodule, tag: dev, add:

Re: [ansible-project] Docker module does not restart containers when docker parameters have changed

Understood. I'm still working on it. I will definitely send PR when I am ready. Aaron On Thursday, October 2, 2014, Michael DeHaan mich...@ansible.com wrote: Just a note - please send in a PR if you have something, if you just send me the diff on your branch and master, we won't have it in

Re: [ansible-project] Docker module does not restart containers when docker parameters have changed

Here's the code change to restart the container if env vars have changed: https://github.com/forty9ten/ansible-modules-core/compare/ansible:devel...devel Let me know what you think. I know in the previous post I also talked about also checking other parameters such as volume and port. Maybe

Re: [ansible-project] docker module is not upgrading my container

Assuming that: 1) The kill old container task isn't supposed to be present in the second example 2) The snazzy/cyweb container is running a long running process 3) Manually running docker's tools does something similar I think this behaviour is intended. This seems like we're just

Re: [ansible-project] docker module is not upgrading my container

On Mon, Sep 29, 2014 at 1:53 PM, Jazzed brian.flem...@cyaninc.com wrote: Assuming that: 1) The kill old container task isn't supposed to be present in the second example 2) The snazzy/cyweb container is running a long running process 3) Manually running docker's tools does something similar

Re: [ansible-project] docker module is not upgrading my container

Thanks for that explanation, Toshio. That helps things a lot. And thanks for tracing through the code too! If this is just a bug, then a fix would be nice. What I was hoping for is for the docker module to detect a new version is available. Then I could do a dry-run and check if any of my

Re: [ansible-project] docker module is not upgrading my container

On Thu, Sep 25, 2014 at 5:36 PM, Brian Fleming brian.flem...@cyaninc.com wrote: My understanding is if I have a playbook that says - hosts: localhost sudo: yes tasks: - name: ensure redis container is running docker: image=dockerfile/redis name=redis command= bash -c

[ansible-project] docker module - what is the syntax for 'volumes' parameter

Hi : What is the syntax for the volumes parameter in the docker module?. There is no example. Assume that I have a host dirs at /opt/my_logs1 and /opt/my_logs2 and I want to map it to a container volumes at /opt/logs1 and /opt/logs2 respectively. So what would the syntax be? Pls advise.

[ansible-project] docker module is not upgrading my container

My understanding is if I have a playbook that says - hosts: localhost sudo: yes tasks: - name: ensure redis container is running docker: image=dockerfile/redis name=redis command= bash -c 'redis-server /etc/redis/redis.conf' - name: ensure web container is running docker:

[ansible-project] Docker module does not restart containers when docker parameters have changed

Currently the docker module only restarts the container if the name parameter is specified and the image has changed. Are there plans to also check if other docker parameters have changed such as env, port and volume? It is pretty common to pass in configuration information via environment

Re: [ansible-project] Docker module does not restart containers when docker parameters have changed

There are no plans per se but that doesn't mean it's not a good idea. I think it would depend on whether this was easily queryable by docker-py, but I imagine it would be. If you'd like to work on this, you are welcome, otherwise please file a feature request in GitHub so we don't lose track of

[ansible-project] Docker module - idempotence problem

Hi all! I've found, that if run such command: - docker: image=registry state=running And then: - docker: image=registry state=runningenv=SOMEVAR=1 The module will return ok, not changed and docker container will not be relaunched with new parameters. At first sight it may seem like

Re: [ansible-project] Docker module - idempotence problem

That parameter is probably intended to be set only at launch time, and is not so much an idempotence problem so much as it's probably not changing anything. Worth checking. Idempotence is a frequently misunderstood concept, which is why we try to not use the word very much. It only means that

Re: [ansible-project] Docker module - idempotence problem

I use Ansible 1.7.1 Can you express your agumentation in application to the specific problem with docker module and evn. vars? Regarding idempotence concept - seems like you right. By the way I think I've found a workaround - instead of env. vars there is possible to use a config file, so

Re: [ansible-project] docker module

Docker images in private repos should have be accessed by the private repo's FQDN, for example: docker.example.com/myimage:tag When pulling by this image name, it's implied that the registry is at docker.example.com and is accessible to the Docker host. It looks like the Docker module makes

[ansible-project] docker module

Hi, Is there a way to pass the docker-module a set of parameters so that it can login to a repository to download private repos. Currently I have it downloading public ones ok but I can not get our private ones to pull. Thanks Mark -- MARK OLLIVERHEAD OF IT OPERATIONS T. +44(0) 20 7775 5628