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
Dear Diego,
I followed your instructions and baked the Docker images successfully:
Successfully built 8872e86df8a3
Successfully tagged diegopacheco/dynomitedocker:latest
then tried to start a single cluster, again it worked:
[root@dynomite-docker]# ./dynomite-docker.sh run_single 0.5.8
0.5.8
Docker images and Network clean up DONE.
ea9d97648bce71cd062250aa379b05b86a3fa38c8524caf5be4e90a500ba464c
NETWORK ID NAME DRIVER SCOPE
dbda5cfb55ae bridge bridge local
11391e02b5bd docker_default bridge local
c7ae52459c21 docker_gwbridge bridge local
496ddf94ecff host host local
cbfdy8y2hxdc ingress overlay swarm
ea9d97648bce myDockerNetDynomite bridge local
127ac754f78d none null local
472bd61e883c787a01d404c7bc9996351ad2c203563fa5f5591a64bc4de309b2
cadacc942a0e96244e42eb74ac6d1ebc47e93cba65c92daca22760b5c5c352a0
1de9b70fd87f51e96683a10ef61d9d73c4fdf586e3bf3e4d0121ac4425c08332
Cluster 2 Single - Topology :
token: 100 dc: dc
rack1 - 179.18.0.101
rack2 - 179.18.0.102
rack3 - 179.18.0.103
Seeds: 179.18.0.101:8102:rack1:dc:100|179.18.0.102:8102:rack2:dc:100|179.18.0.103:8102:rack3:dc:100
Avaliable Dynomite version: v0.5.7, v0.5.8, v0.5.9, v0.6.0
[root@dynomite-docker]#
[root@dynomite-docker]#
[root@dynomite-docker]#
[root@dynomite-docker]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1de9b70fd87f diegopacheco/dynomitedocker "/usr/local/dynomite…" 40 seconds ago Up 39 seconds 6379/tcp, 8101-8102/tcp, 22222/tcp dynomite3
cadacc942a0e diegopacheco/dynomitedocker "/usr/local/dynomite…" 41 seconds ago Up 39 seconds 6379/tcp, 8101-8102/tcp, 22222/tcp dynomite2
472bd61e883c diegopacheco/dynomitedocker "/usr/local/dynomite…" 42 seconds ago Up 40 seconds 6379/tcp, 8101-8102/tcp, 22222/tcp dynomite1
Now the cherry on top would be to take advantage of the Swarm cluster that this node is actually a master of and deploy the 3 instances across the Swarm. Is it something supported out of the box, or somewhat easily achievable?
Thank you so much,
Roberto
The text was updated successfully, but these errors were encountered:
Dear Diego,
I followed your instructions and baked the Docker images successfully:
then tried to start a single cluster, again it worked:
Now the cherry on top would be to take advantage of the Swarm cluster that this node is actually a master of and deploy the 3 instances across the Swarm. Is it something supported out of the box, or somewhat easily achievable?
Thank you so much,
Roberto
The text was updated successfully, but these errors were encountered: