Netflix 导体服务器本地 docker 容器不健康

Netflix conductor server local docker container is unhealthy

我正在按照步骤 here to install & run Netflix Conductor locally on my desktop. I am trying to use docker-compose to bring all the services up. After initial problems of incorrect docker version, docker compose version, docker compose build problem (solved using this)，我遇到了这个错误的障碍 -

/conductor/docker$ sudo docker-compose up

docker_elasticsearch_1 is up-to-date

docker_dynomite_1 is up-to-date

ERROR: for conductor-server Container "a89b4c61d465" is unhealthy.

ERROR: Encountered errors while bringing up the project.

我还在 docker-compose.yaml、server/config/config.properties & server/config/config-local.properties.

中将 elasticsearch 端口更改为 10300

Docker compose 版本为 1.23.2。 Docker 版本为 18.09.3。

PS：我对 docker 及相关概念非常陌生。

更多信息：将我的端口更改恢复为默认值 (9200/9300) 并添加了 docker 不健康容器的信息（docker 容器 ID 由于重建而更改）

/conductor/docker$ sudo docker ps -a --filter "id=7be9f9b5288c" [sudo] password for anshuman: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

7be9f9b5288c docker.elastic.co/elasticsearch/elasticsearch:5.6.8 "/bin/bash bin/es-do…" 36 minutes ago Up 36 minutes (unhealthy) 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp docker_elasticsearch_1

curl 到 elasticsearch 似乎没问题。

/conductor/docker$ curl http://127.0.0.1:9200/_cat/health 1553188720 17:18:40 docker-cluster yellow 1 1 5 5 0 0 5 0 - 50.0%

Docker 容器的日志给了我这个（不知道它们是什么意思）

/conductor/docker$ sudo docker logs 7be9f9b5288c [2019-03-21T17:12:06,323][INFO ][o.e.x.m.MachineLearningTemplateRegistry] [M5hkiIZ] successfully created .ml-meta index template

[2019-03-21T17:12:06,413][INFO ][o.e.x.m.MachineLearningTemplateRegistry] [M5hkiIZ] successfully created .ml-notifications index template

[2019-03-21T17:12:06,502][INFO ][o.e.x.m.MachineLearningTemplateRegistry] [M5hkiIZ] successfully created .ml-anomalies- index template

[2019-03-21T17:12:07,152][INFO ][o.e.l.LicenseService ] [M5hkiIZ] license [dfac41a4-9280-4c77-81ef-0f943039ef77] mode [trial] - valid

[2019-03-21T17:12:15,712][INFO ][o.e.c.m.MetaDataCreateIndexService] [M5hkiIZ] [.monitoring-es-6-2019.03.21] creating index, cause [auto(bulk api)], templates [.monitoring-es], shards 1/1, mappings [doc]

[2019-03-21T17:12:16,122][INFO ][o.e.c.m.MetaDataCreateIndexService] [M5hkiIZ] [.watches] creating index, cause [auto(bulk api)], templates [watches], shards 1/1, mappings [watch]

[2019-03-21T17:12:16,728][INFO ][o.e.c.m.MetaDataMappingService] [M5hkiIZ] [.watches/t05gsw2UQjmWEJ9IiSKn6g] update_mapping [watch]

[2019-03-21T17:13:17,111][INFO ][o.e.c.m.MetaDataCreateIndexService] [M5hkiIZ] [.triggered_watches] creating index, cause [auto(bulk api)], templates [triggered_watches], shards 1/1, mappings [triggered_watch]

[2019-03-21T17:13:17,644][INFO ][o.e.c.m.MetaDataCreateIndexService] [M5hkiIZ] [.monitoring-alerts-6] creating index, cause [auto(bulk api)], templates [.monitoring-alerts], shards 1/1, mappings [doc]

[2019-03-21T17:13:17,918][INFO ][o.e.c.m.MetaDataCreateIndexService] [M5hkiIZ] [.watcher-history-6-2019.03.21] creating index, cause [auto(bulk api)], templates [.watch-history-6], shards 1/1, mappings [doc]

[2019-03-21T17:13:18,475][INFO ][o.e.c.m.MetaDataMappingService] [M5hkiIZ] [.watcher-history-6-2019.03.21/sP8OvfXNSmCImfRf3mCR3A] update_mapping [doc]

[2019-03-21T17:13:18,718][INFO ][o.e.c.m.MetaDataMappingService] [M5hkiIZ] [.watcher-history-6-2019.03.21/sP8OvfXNSmCImfRf3mCR3A] update_mapping [doc]

最后，我找出了使这项工作可行的问题。它需要 uired 至少了解 docker 和 Dockerfile 的工作原理。

  1. 根据文档 here，我启动了本地服务器并尝试使用 docker-compose 启动所有内容。这给了我一个端口冲突。
  2. 我错误地更改了 elasticsearch 的端口。在学习 Dockerfile 的基础知识后意识到这一点。这就是我容器不健康的原因。

  3. 然后building conductor-ui.

    有错误

    npm ERR! code EINTEGRITY

    此要求ui红色 Dockerfile 中的导体-ui 发生变化。 npm install 命令更改为 npm install --no-shrinkwrap --update-binary（基于答案 ). Other answers for this issue