监视JHipster错误启动jhipster警报器

Question

我已经根据这个链接安装了开箱即用的监控：

http://www.jhipster.tech/monitoring/

当我开始的时候：

docker-compose up -d

一切开始，但不是Elastalert：

First log:

错误: for monitoring_jhipster alerter_1无法启动服务jhipster alerter: OCI运行时创建失败: container_linux.go:296:启动容器进程导致"process_linux.go:398: container init caused \"rootfs_linux.go:58:正在将\"/Users/john/source/intellij/company/app/myservice/alerts/config.yaml\“挂载到位于\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged/opt/elastalert/config的根文件系统\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged\”.yaml\“原因\”不是目录\“\”：未知:您是否正在尝试挂载导入监控监控_jhipster direStarting -dashboard_1

Second log:

错误:对于jhipster-alerter无法启动服务jhipster-alerter: OCI运行时创建失败: container_linux.go:296:启动容器进程导致"process_linux.go:398: container init caused \"rootfs_linux.go:58:正在将\"/Users/john/source/intellij/company/app/myservice/alerts/config.yaml\“挂载到位于\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged/opt/elastalert/config.yaml\”的rootfs \"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged\“导致\“不是目录\”\“”：未知:您是否正在尝试将目录挂载到文件上(反之亦然)？检查指定的主机路径是否存在以及是否为预期类型错误:启动项目时遇到错误。

使用我获得的默认docker-compose.yml文件：

curl -O https://raw.githubusercontent.com/jhipster/jhipster-console/master/bootstrap/docker-compose.yml

我不确定这条消息说了什么？

Answer 1

这是因为JHipster Alerter的卷路径不正确。变化

jhipster-alerter:
    image: jhipster/jhipster-alerter:latest
    environment:
        - ES_HOST=jhipster-elasticsearch
        - ES_PORT=9200
    volumes:
        - ../jhipster-alerter/rules/:/opt/elastalert/rules/
        - ../alerts/config.yaml:/opt/elastalert/config.yaml

至

        - ../alerts/rules/:/opt/elastalert/rules/
        - ../jhipster-alerter/config.yaml:/opt/elastalert/config.yaml

如https://github.com/jhipster/jhipster-console/pull/102/commits/fa5bc75ec29ca357477ac1a22203ae6cbe2af2f7所示。