-
Notifications
You must be signed in to change notification settings - Fork 1.9k
docker_container never starts containers #5774
Comments
@ansible ping, this issue is waiting for your response. |
I'm seeing the exact same issue. Container with state "started" creates a container with a generic Docker assigned name instead of one specified in Ansible, and with "created" status instead of running. I'm running Ansible 2.2.0.0 with docker-py 1.10.6:
results in a Docker container with a generic name like "hungy_tesla" and STATUS of "Created" instead of "Running". |
same issue |
As per the links @marcosnils provided, the issue is with |
Just install a 2.11.x version of |
I think you mean 2.11.x, 1.11.x doesn't exist and I just tried with 2.11.1 and works. |
Yeah, sorry, @juanluisbaptiste; I stand corrected |
i am facing the same issue. Using requests (2.11.1) Fedora 26 any help |
ISSUE TYPE
COMPONENT NAME
docker_container
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
Containers are created with the wrong name, outside network and never start
STEPS TO REPRODUCE
Run a playbook that does the following:
EXPECTED RESULTS
A container named
new-container
running, and in themy_networ
networkACTUAL RESULTS
Container with generic name is
Created
outside network, not runningansible
-vvvvv
outputdockerd -D
outputdocker ps -a
yields:According to the docker daemon logs, the daemon never gets the
/start
instruction, just the/create
The text was updated successfully, but these errors were encountered: