Docker Community Forums

Share and learn in the Docker community.

Autoredeploy feature dont seams to works


(Clément Garnier) #1

Hello,
I m trying to setup a service with the auro redeploy feature on my own node.
When i push a new image, i get this error;

ERROR: test-f170a48b-1: Conflict. The name “test-f170a48b-1.f26dcc52” is already in use by container 91088cd790e6. You have to remove (or rename) that container to be able to reuse that name.
ERROR: Service Redeploy (autoredeploy on push) action on ‘test-f170a48b’ (using ‘cgarnier/test:latest’) has failed

Any idea ?


(Borja Burgos) #2

We are unable to reproduce this issue. Can you please provide more info?


(Clément Garnier) #3

I made a simple service, i use my own image on docker hub.
When i push a new one, the redeploy is well triggered. But it fail with the message above.

I jsut figure out that there is an other issue with my node. Docker Cloud is unable to reach it for unknow reason.

It s a fresh node. I just reset the machine for use it on Cloud. I use the “bring your own node” script to setup it. It s hosted in France by ovh.com

Debian 8 3.14.32-xxxx-grs-ipv6-64

Docker info:
Containers: 15
Images: 88
Server Version: 1.9.1-cs2
Storage Driver: devicemapper
Pool Name: docker-8:2-785300-pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem:
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 1.583 GB
Data Space Total: 107.4 GB
Data Space Available: 18.17 GB
Metadata Space Used: 4.837 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.143 GB
Udev Sync Supported: false
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.14.32-xxxx-grs-ipv6-64
Operating System: Debian GNU/Linux 8 (jessie)
CPUs: 4
Total Memory: 3.834 GiB
Name: ns334457.ip-5-196-65.eu
ID: BQB5:PCJA:W5X6:O4VU:6HQJ:X3P6:BYZ7:4JKU:TX3F:YEQ3:VGAK:XN5I

docker agent logs:

tail /var/log/dockercloud/agent.log
2016/02/17 09:15:41 Starting docker daemon: [/usr/lib/dockercloud/docker daemon -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --userland-proxy=false --tlscert /etc/dockercloud/agent/cert.pem --tlskey /etc/dockercloud/agent/key.pem --tlscacert /etc/dockercloud/agent/ca.pem --tlsverify]
2016/02/17 09:15:41 Docker unix socket opened
2016/02/17 09:15:41 Docker daemon (PID:4708) has been started
2016/02/17 09:15:41 Node e5c21542-b33a-4c68-8de2-ca39b2396663.node.dockerapp.io is NOT publicly reachable
2016/02/17 09:15:42 Ngrok server: tunnel02.cloud.docker.com:4443
2016/02/17 09:15:42 Starting NAT tunnel
2016/02/17 09:20:41 Node registration to https://cloud.docker.com/ succeeded
2016/02/17 09:59:45 Found new tunnel: tcp://tunnel02.cloud.docker.com:47097
2016/02/17 09:59:45 Sending tunnel address to Docker Cloud
2016/02/17 09:59:46 New tunnel has been set up

(Fernando Mayo) #4

It seems that we are getting network issues when trying to reach your node. Your node is not publicly reachable and we are setting a tunnel up, but even with that, network connectivity seems intermittent. Can you paste your “/var/log/dockercloud/ngrok.log”?

In order to rule out the reverse tunnel being the source of the issue, can you open port 2375 in your firewall and restart the agent? (The port is TLS secured so only Docker Cloud can access it)


(Clément Garnier) #5

I dont have firewall.

http://pastebin.com/DnQbNbhf

Tunnel fail some time


(Clément Garnier) #6

http://pastebin.com/mLCw7BUV


(Fernando Mayo) #7

It seems that the DNS your server is using is having issues resolving the tunnel address (tunnel02.cloud.docker.com). In any case, now that your docker port is publicly accessible, I have removed the tunnel configuration.


(Clément Garnier) #8

thank you! I will retry the autoredeploy feature to see if it solved my other issue too =)


(Clément Garnier) #9
ERROR: moldmon-api-1: Conflict. The name "moldmon-api-1.moldmon2.85a2cdea" is already in use by container 63bcca0c62de. You have to remove (or rename) that container to be able to reuse that name. 
ERROR: Service Redeploy (autoredeploy on push) action on 'moldmon-api' (using 'cgarnier/moldmon-api:latest') has failed

I got the same issue :confused:

That s my stack:

 lb:
  image: 'dockercloud/haproxy:latest'
  links:
    - moldmon-api
  ports:
    - '80:80'
  roles:
    - global
moldmon-api:
  image: 'cgarnier/moldmon-api:latest'
  autoredeploy: true
  sequential_deployment: true
  target_num_containers: 2

This time, one of the both container started the other one fail this the name conflict issue.
My ci has just pushed a new version of the image.

This is how i process:

 script:
     - docker build -t moldmon-api .
     - docker tag moldmon-api cgarnier/moldmon-api:latest
     - docker push cgarnier/moldmon-api:latest

(Borja Burgos) #10

This (name conflict) appears to be an engine related issue that we’re investigating and are having trouble reproducing at this time. Are you continuing to consistenly experience this issue?


(Clément Garnier) #11

I will restart the stack an make a try


(Clément Garnier) #12
`moldmon-api-1: Stopping gracefully (Timeout 10s)...
moldmon-api-1: Terminating...
moldmon-api-1: Terminated
moldmon-api-1: Deploying in e5c21542-b33a-4c68-8de2-ca39b2396663.node.dockerapp.io
moldmon-api-1: Creating in e5c21542-b33a-4c68-8de2-ca39b2396663.node.dockerapp.io with docker name moldmon-api-1.autoredeploy-test.161901bc
ERROR: moldmon-api-1: Conflict. The name "moldmon-api-1.autoredeploy-test.161901bc" is already in use by container dcca738fa7f7. You have to remove (or rename) that container to be able to reuse that name.
ERROR: Service Redeploy (autoredeploy on push) action on 'moldmon-api' (using 'cgarnier/moldmon-api:latest') has failed`

yes, same issue


(Borja Burgos) #13

This has been identified as an issue in the core, open source, Docker Engine. We continue to investigate.