Skip to content
This repository has been archived by the owner on Aug 14, 2019. It is now read-only.

Error response from daemon: Conflict with container name /coordinator... #7

Open
rm-rf-etc opened this issue Jun 18, 2018 · 1 comment

Comments

@rm-rf-etc
Copy link

rm-rf-etc commented Jun 18, 2018

Is this being caused by requesting only 1 machine? Is there a minimum number of machines using this approach?

rob::Roberts-iMac { ~/projects/Deployment/arangodb }-> ./DigitalOcean_ArangoDB_Cluster.sh -n 1 -m 1gb -z sfo2
REGION: sfo2
SIZE: 1gb
NUMBER OF MACHINES: 1
OUTPUT DIRECTORY: digital_ocean
MACHINE PREFIX: arangodb-test-69610-

ArangoDB SSH-Key found. Try to use /Users/rob/.ssh/arangodb_do_key.pub
Fetched deposited keys from digital ocean.
SSH-Key is valid and already stored at digital ocean.
SSH-Agent is running.
SSH-Key already added to SSH-Agent
creating machine arangodb-test-69610-1
Machine arangodb-test-69610-1 created.
Getting status information from machine: arangodb-test-69610-1.
Getting status information from machine: arangodb-test-69610-1.
Machine information from arangodb-test-69610-1 fetched.
Machine arangodb-test-69610-1 finished
All machines are set up
Internal IPs: 10.138.XX.XX
External IPs: 178.128.XXX.XXX
IDs : 98264830
Remove host key entries in /Users/rob/.ssh/known_hosts...
Host 178.128.XXX.XXX not found in /Users/rob/.ssh/known_hosts
SERVERS_EXTERNAL: 178.128.XXX.XXX
SERVERS_INTERNAL: 10.138.XX.XX
Number of DBServers: 1
Number of Coordinators: 1
SSH_CMD=ssh
SSH_ARGS=-oStrictHostKeyChecking no
SSH_USER=core
PORT_DBSERVER=8629
PORT_COORDINATOR=8529
PORT_REPLICA=8630
COORDINATOR_MACHINES:0 0 0
FIRST_COORDINATOR: 0
DBSERVER_DATA=/home/core/dbserver
DBSERVER_LOGS=/home/core/dbserver_logs
REPLICA_DATA=/home/core/replica
REPLICA_LOGS=/home/core/replica_logs
AGENCY_DIR=/home/core/agency
COORDINATOR_DATA=/home/core/coordinator_data
COORDINATOR_LOGS=/home/core/coordinator_logs
Creating directories on servers. This may take some time. Please wait.
Starting agency...
Unable to find image 'm0ppers/arangodb:3.0' locally
3.0: Pulling from m0ppers/arangodb
03e1855d4f31: Pulling fs layer
a3ed95caeb02: Pulling fs layer
50621e5380be: Pulling fs layer
36d83ceabf93: Pulling fs layer
30086e7a828d: Pulling fs layer
ae7c7df1a47f: Pulling fs layer
068ab8db2852: Pulling fs layer
a7bff4d6f809: Pulling fs layer
36d83ceabf93: Waiting
30086e7a828d: Waiting
ae7c7df1a47f: Waiting
068ab8db2852: Waiting
a7bff4d6f809: Waiting
a3ed95caeb02: Verifying Checksum
a3ed95caeb02: Download complete
50621e5380be: Verifying Checksum
50621e5380be: Download complete
36d83ceabf93: Verifying Checksum
36d83ceabf93: Download complete
03e1855d4f31: Verifying Checksum
03e1855d4f31: Download complete
ae7c7df1a47f: Verifying Checksum
ae7c7df1a47f: Download complete
a7bff4d6f809: Verifying Checksum
a7bff4d6f809: Download complete
30086e7a828d: Verifying Checksum
30086e7a828d: Download complete
068ab8db2852: Verifying Checksum
068ab8db2852: Download complete
03e1855d4f31: Pull complete
a3ed95caeb02: Pull complete
50621e5380be: Pull complete
36d83ceabf93: Pull complete
30086e7a828d: Pull complete
ae7c7df1a47f: Pull complete
068ab8db2852: Pull complete
a7bff4d6f809: Pull complete
Digest: sha256:----------------------------------------------------------------
Status: Downloaded newer image for m0ppers/arangodb:3.0
----------------------------------------------------------------
Starting DBserver on 178.128.XXX.XXX:8629
----------------------------------------------------------------
Starting Coordinator on 178.128.XXX.XXX:8529
Starting Coordinator on 178.128.XXX.XXX:8529
Starting Coordinator on 178.128.XXX.XXX:8529
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
Error in remote docker run, retrying...
Error in remote docker run, retrying...
63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
Error in remote docker run, retrying...
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
Error in remote docker run, retrying...
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
Error in remote docker run, retrying...
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
/run/torcx/bin/docker: Error response from daemon: Conflict. The container name "/coordinator8529" is already in use by container "63fda243b3771713f7b7eea3996bfb40d98562992f9d1b0d0b28711878e6c044". You have to remove (or rename) that container to be able to reuse that name.
See '/run/torcx/bin/docker run --help'.
Error in remote docker run, retrying...
Error in remote docker run, retrying...
@daviwu
Copy link

daviwu commented Aug 14, 2018

I have the same problem, probably a bug in the script for the loop.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants