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
Got it right and tagged the result container with my private repository (PRIVATE:5000/arangodb-starter:3.1.9
Pushed the container and on the target first machine tried to run it
Found that creating a volume require --name as a flag before the name (would be nice if that can be fixed)
The container started and gave me the running commands for the 2 additional nodes
Found that the command generator doesn't take in account that I'm using a private registry and gave me the path to docker.io hub registry - would be nice to have either the arangodb-starter container in arangodb registry (it doesn't exist) or the generator take the private image registry
I've run the 2 additional nodes, things seems to be nice but after 5 minutes got errors in the terminal of all 3 nodes:
First node (the original one)
2017/02/02 13:32:29 Listening on 0.0.0.0:4000
2017/02/02 13:36:14 New peer: xxx.xx.xx.189, portOffset: 5
2017/02/02 13:37:24 New peer: xxx.xx.xx.189, portOffset: 10
2017/02/02 13:37:25 Starting service...
2017/02/02 13:37:25 Starting agent on port 4001
2017/02/02 13:37:26 Starting dbserver on port 4003
2017/02/02 13:37:27 Starting coordinator on port 4002
2017/02/02 13:37:28 agent up and running.
2017/02/02 13:39:58 dbserver not ready after 5min!
2017/02/02 13:39:59 coordinator not ready after 5min!
Second and third nodes are the same (except for the IPs obviously so here is a snippet of one)
2017/02/02 13:36:14 Contacting master xxx.xx.xx.189:4000...
2017/02/02 13:36:14 Waiting for 3 servers to show up...
2017/02/02 13:36:14 Listening on 0.0.0.0:4000
2017/02/02 13:37:25 Starting service...
2017/02/02 13:37:25 Starting agent on port 4006
2017/02/02 13:37:26 Starting dbserver on port 4008
2017/02/02 13:37:27 Starting coordinator on port 4007
2017/02/02 13:39:57 agent not ready after 5min!
2017/02/02 13:39:58 dbserver not ready after 5min!
2017/02/02 13:39:59 coordinator not ready after 5min!
All containers exist on all 3 nodes as expected:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
db4d5001f7d0 arangodb/arangodb:3.1.9 "/usr/sbin/arangod -c" 11 minutes ago Up 11 minutes 0.0.0.0:4002->4002/tcp, 0.0.0.0:32770->8529/tcp coordinator-0-0-xxx.xx.xx.189-4002
74204e4fa98d arangodb/arangodb:3.1.9 "/usr/sbin/arangod -c" 11 minutes ago Up 11 minutes 0.0.0.0:4003->4003/tcp, 0.0.0.0:32769->8529/tcp dbserver-0-0-xxx.xx.xx.189-4003
05db4d39b8b4 arangodb/arangodb:3.1.9 "/usr/sbin/arangod -c" 11 minutes ago Up 11 minutes 0.0.0.0:4001->4001/tcp, 0.0.0.0:32768->8529/tcp agent-0-xxx.xx.xx.189-4001
a1009d4220b6 PRIVATE:5000/arangodb-starter:latest "/app/arangodb-linux-" 16 minutes ago Up 16 minutes 0.0.0.0:4000->4000/tcp, 8529/tcp adb1
The text was updated successfully, but these errors were encountered:
Reproduce
make docker
First node (the original one)
Second and third nodes are the same (except for the IPs obviously so here is a snippet of one)
All containers exist on all 3 nodes as expected:
The text was updated successfully, but these errors were encountered: