Neo4j HA模型在Docker中不起作用

我正在尝试使用Azure Container Service + Docker在HA模式下运行Neo4j。 运行模式是同一networking中的HA 3个实例所必需的。

我用命令创build一个networking:

dockernetworking创build – 驱动程序=桥集群

但是,当试图关联这个networking的实例时,我得到了以下错误:

docker:来自守护进程的错误响应:找不到networking集群。

我已经尝试了networkingID,不起作用。

我正在学习这个教程: https : //neo4j.com/developer/docker-3.x/,但没有成功。 小费小费?

ps。:以单独模式运行。

我得到的命令和结果。

jefersonanjos @ swarm-master-21858A81-0:〜/ neo4j / data $ docker network create –driver = bridge cluster
结果:d9fb3dd121ded5bfe01765ce4d276b75ad4e66ef1f2bd62b858a2cea86ccc1ec

jefersonanjos @ swarm-master-21858A81-0:〜/ neo4j / data $ docker run –name = instance1 –detach –publish = 7474:7474 –publish = 7687:7687 –net = cluster –hostname = instance1 \ – env = NEO4J_dbms_mode = HA –env = NEO4J_ha_serverId = 1 \ – env = NEO4J_ha_host_coordination = instance1:5001 –env = NEO4J_ha_host_data = instance1:6001 \ – env = NEO4J_ha_initialHosts = instance1:5001,instance2:5001,instance3 :5001 \ neo4j:企业成绩:b57ca9a895535b07ef97d956a780b9687e7384b33f389e2470e0ed743c79ef11

jefersonanjos @ swarm-master-21858A81-0:〜/ neo4j / data $ docker run –name = instance2 –detach –publish 7475:7474 –publish = 7688:7687 –net = cluster –hostname = instance2 \ –env = NEO4J_dbms_mode = HA –env = NEO4J_ha_serverId = 2 \ – env = NEO4J_ha_host_coordination = instance2:5001 – env = NEO4J_ha_host_data = instance2:6001 \ – env = NEO4J_ha_initialHosts = instance1:5001,instance2:5001,instance3: 5001 \ neo4j:企业docker:来自守护程序的错误响应:找不到networking集群。 参见“docker运行 – 帮助”。

jefersonanjos @ swarm-master-21858A81-0:〜/ neo4j / data $ docker run –name = instance3 –detach –publish 7476:7474 –publish = 7689:7687 –net = cluster –hostname = instance3 \ –env = NEO4J_dbms_mode = HA –env = NEO4J_ha_serverId = 3 \ – env = NEO4J_ha_host_coordination = instance3:5001 – env = NEO4J_ha_host_data = instance3:6001 \ –env = NEO4J_ha_initialHosts = instance1:5001,instance2:5001,instance3: 5001 \ neo4j:企业08c4c5156dc8bb589f4c876de3a2bf0170450ae640606d505e1851da94220d7e

docker工人在azure色的问题是因为我正在做一个机器集群的testing。

所以命令:docker network create –driver = bridge cluster不用于这个目的。

我们必须使用–driver = overlay作为多主机。

Mor info: https : //docs.docker.com/engine/userguide/networking/get-started-overlay/