- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我需要将单个 YML 文件拆分为多个 YML 文件:
微服务.yml:
#-------------------------------------------------------------
#- Docker compose base definition file to run containers.
#-----------------------------------------------------------
---
version: '3.6'
services:
db-service1:
build:
context: ${MONGO_DB_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
container_name: 'mongo1'
ports:
- "30001:27017"
db-service2:
build:
context: ${MONGO_DB_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
container_name: 'mongo2'
ports:
- "30002:27017"
db-service3:
build:
context: ${MONGO_DB_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
container_name: 'mongo3'
ports:
- "30003:27017"
mongosetup:
container_name: 'mongoinit'
build:
context: ${MONGO_INIT_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
depends_on:
- db-service1
- db-service2
- db-service3
api:
build:
context: ${API_CONTEXT}
dockerfile: Dockerfile
args:
API_BASE_IMAGE: ${API_BASE_IMAGE}
api_artifactid: ${api_artifactid}
api_java_options: ${java_options} ${REMOTE_DEBUG}
image: ${API_IMAGE}
depends_on:
- db-service1
- db-service2
- db-service3
ports:
- "9096:8080"
- "40508:40500"
environment:
DATABASE_KEY: mongodb
MONGODB_DBNAME: ms_eventclassification
MONGODB_CONNECTIONSTR: mongodb://mongo1:27017,mongo2:27017,mongo3:27017
temn.msf.security.authz.enabled: "false"
temn.entitlement.service.enabled: "false"
class.inbox.dao: com.myproject.microservice.framework.core.inbox.InboxDaoImpl
class.outbox.dao: com.myproject.microservice.framework.core.outbox.OutboxDaoImpl
className_GetDictionary: com.myproject.microservice.eventclassification.function.GetDictionaryImpl
className_ClassifyEvnts: com.myproject.microservice.eventclassification.function.ClassifyEvntsImpl
className_UpdateDictionary: com.myproject.microservice.eventclassification.function.UpdateDictionaryImpl
className_PutMessagesToTopic: com.myproject.microservice.eventclassification.function.PutMessagesToTopicImpl
temn.msf.name: ms_eventclassification
temn.msf.stream.vendor: kafka
temn.msf.stream.kafka.bootstrap.servers: kafka:29092
temn.msf.ingest.outbox.cache.namespace: eventclassification-outbox
tmn.ignite.host: cache-service
tmn.ignite.port: 10800
inboxingester:
build:
context: ${INGESTER_CONTEXT}
dockerfile: Dockerfile
args:
BASE_IMAGE: ${INGESTER_APP_BASE_IMAGE}
artifactid: ${ingester_artifactid}
java_options: ${java_options} ${REMOTE_DEBUG}
image: ${INGESTER_IMAGE}
depends_on:
- db-service1
- db-service2
- db-service3
ports:
- "40500:40500"
environment:
DATABASE_KEY: mongodb
MONGODB_DBNAME: ms_eventclassification
MONGODB_CONNECTIONSTR: mongodb://mongo1:27017,mongo2:27017,mongo3:27017
temn.msf.name: ms-eventclassification
temn.msf.stream.vendor: kafka
temn.msf.stream.kafka.bootstrap.servers: kafka:29092
temn.msf.ingest.source.stream: ms-eventclassification-inbox-topic
temn.msf.ingest.source.stream.consumergroup.id: ms-eventclassification-ingester-consumer
temn.msf.ingest.sink.error.enabled: "false"
temn.msf.ingest.sink.error.stream.producer.id: ms-eventclassification-ingester-error-producer
temn.msf.ingest.generic.ingester: com.myproject.microservice.framework.core.ingester.GenericCommandBinaryIngester
temn.msf.exec.env: server
temn.msf.raise.received.event: "true"
class.inbox.dao: com.myproject.microservice.framework.core.inbox.InboxDaoImpl
class.outbox.dao: com.myproject.microservice.framework.core.outbox.OutboxDaoImpl
temn.msf.ingest.is.avro.event.ingester: "false"
temn.msf.security.authz.enabled: "false"
temn.msf.ingest.outbox.cache.namespace: eventclassification-outbox
tmn.ignite.host: cache-service
tmn.ignite.port: 10800
temn.msf.ingest.inbox.cache.namespace: eventclassification-inbox
inboxoutboxprocessorapp:
build:
context: ${INBOXOUTBOX_CONTEXT}
dockerfile: Dockerfile
args:
BASE_IMAGE: ${INBOXOUTBOX_BASE_IMAGE}
artifactid: ${inboxoutbox_artifactid}
java_options: ${java_options} ${REMOTE_DEBUG}
image: ${INBOXOUTBOX_IMAGE}
depends_on:
- cache-service
ports:
- "40514:40500"
environment:
DATABASE_KEY: mongodb
MONGODB_DBNAME: ms_eventclassification
MONGODB_CONNECTIONSTR: mongodb://mongo1:27017,mongo2:27017,mongo3:27017
temn.msf.name: ms-eventclassification
temn.msf.stream.vendor: kafka
temn.msf.stream.kafka.bootstrap.servers: kafka:29092
temn.msf.exec.env: server
temn.msf.stream.outbox.topic:
temn.msf.ingest.generic.ingester: com.myproject.microservice.framework.core.ingester.GenericCommandBinaryIngester
temn.msf.function.class.ClassifyEvnts: com.myproject.microservice.eventclassification.function.ClassifyEvntsImpl
temn.msf.function.class.UpdateDictionary: com.myproject.microservice.eventclassification.function.UpdateDictionaryImpl
temn.msf.function.class.PutMessagesToTopic: com.myproject.microservice.eventclassification.function.PutMessagesToTopicImpl
class.package.name: com.myproject.microservice.eventclassification.function
class.inbox.dao: com.myproject.microservice.framework.core.inbox.InboxDaoImpl
class.outbox.dao: com.myproject.microservice.framework.core.outbox.OutboxDaoImpl
temn.msf.security.authz.enabled: "false"
tmn.inbox.source.namespace: eventclassification-inbox
tmn.outbox.source.namespace: eventclassification-outbox
temn.msf.ingest.outbox.cache.namespace: eventclassification-outbox
tmn.ignite.host: cache-service
tmn.ignite.port: 10800
tmn.inbox.thread.pool.count: 10
tmn.outbox.thread.pool.count: 10
我已将其分成两个文件
我已将所有数据库相关服务复制到数据库 YML 文件,并将摄取相关服务复制到摄取 YML 文件。由于 Ingester 依赖于数据库服务,因此我删除了这些依赖项。我应该确保摄取 YML 仅在数据库服务完全启动并运行时才运行。
db.yml
#-------------------------------------------------------------
#- Docker compose base definition file to run containers.
#-----------------------------------------------------------
---
version: '3.6'
services:
db-service1:
build:
context: ${MONGO_DB_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
container_name: 'mongo1'
ports:
- "30001:27017"
db-service2:
build:
context: ${MONGO_DB_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
container_name: 'mongo2'
ports:
- "30002:27017"
db-service3:
build:
context: ${MONGO_DB_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
container_name: 'mongo3'
ports:
- "30003:27017"
mongosetup:
container_name: 'mongoinit'
build:
context: ${MONGO_INIT_CONTEXT}
dockerfile: Dockerfile
args:
DB_BASE_IMAGE: ${MONGO_DB_BASE_IMAGE}
depends_on:
- db-service1
- db-service2
- db-service3
Ingester.yml
#-------------------------------------------------------------
#- Docker compose base definition file to run containers.
#-----------------------------------------------------------
---
version: '3.6'
services:
inboxingester:
build:
context: ${INGESTER_CONTEXT}
dockerfile: Dockerfile
args:
BASE_IMAGE: ${INGESTER_APP_BASE_IMAGE}
artifactid: ${ingester_artifactid}
java_options: ${java_options} ${REMOTE_DEBUG}
image: ${INGESTER_IMAGE}
ports:
- "40500:40500"
environment:
DATABASE_KEY: mongodb
MONGODB_DBNAME: ms_eventclassification
MONGODB_CONNECTIONSTR: mongodb://mongo1:27017,mongo2:27017,mongo3:27017
temn.msf.name: ms-eventclassification
temn.msf.stream.vendor: kafka
temn.msf.stream.kafka.bootstrap.servers: kafka:29092
temn.msf.ingest.source.stream: ms-eventclassification-inbox-topic
temn.msf.ingest.source.stream.consumergroup.id: ms-eventclassification-ingester-consumer
temn.msf.ingest.sink.error.enabled: "false"
temn.msf.ingest.sink.error.stream.producer.id: ms-eventclassification-ingester-error-producer
temn.msf.ingest.generic.ingester: com.myproject.microservice.framework.core.ingester.GenericCommandBinaryIngester
temn.msf.exec.env: server
temn.msf.raise.received.event: "true"
class.inbox.dao: com.myproject.microservice.framework.core.inbox.InboxDaoImpl
class.outbox.dao: com.myproject.microservice.framework.core.outbox.OutboxDaoImpl
temn.msf.ingest.is.avro.event.ingester: "false"
temn.msf.security.authz.enabled: "false"
temn.msf.ingest.outbox.cache.namespace: eventclassification-outbox
tmn.ignite.host: cache-service
tmn.ignite.port: 10800
temn.msf.ingest.inbox.cache.namespace: eventclassification-inbox
inboxoutboxprocessorapp:
build:
context: ${INBOXOUTBOX_CONTEXT}
dockerfile: Dockerfile
args:
BASE_IMAGE: ${INBOXOUTBOX_BASE_IMAGE}
artifactid: ${inboxoutbox_artifactid}
java_options: ${java_options} ${REMOTE_DEBUG}
image: ${INBOXOUTBOX_IMAGE}
ports:
- "40514:40500"
environment:
DATABASE_KEY: mongodb
MONGODB_DBNAME: ms_eventclassification
MONGODB_CONNECTIONSTR: mongodb://mongo1:27017,mongo2:27017,mongo3:27017
temn.msf.name: ms-eventclassification
temn.msf.stream.vendor: kafka
temn.msf.stream.kafka.bootstrap.servers: kafka:29092
temn.msf.exec.env: server
temn.msf.stream.outbox.topic:
temn.msf.ingest.generic.ingester: com.myproject.microservice.framework.core.ingester.GenericCommandBinaryIngester
temn.msf.function.class.ClassifyEvnts: com.myproject.microservice.eventclassification.function.ClassifyEvntsImpl
temn.msf.function.class.UpdateDictionary: com.myproject.microservice.eventclassification.function.UpdateDictionaryImpl
temn.msf.function.class.PutMessagesToTopic: com.myproject.microservice.eventclassification.function.PutMessagesToTopicImpl
class.package.name: com.myproject.microservice.eventclassification.function
class.inbox.dao: com.myproject.microservice.framework.core.inbox.InboxDaoImpl
class.outbox.dao: com.myproject.microservice.framework.core.outbox.OutboxDaoImpl
temn.msf.security.authz.enabled: "false"
tmn.inbox.source.namespace: eventclassification-inbox
tmn.outbox.source.namespace: eventclassification-outbox
temn.msf.ingest.outbox.cache.namespace: eventclassification-outbox
tmn.ignite.host: cache-service
tmn.ignite.port: 10800
tmn.inbox.thread.pool.count: 10
tmn.outbox.thread.pool.count: 10
这是正确的方法吗?
最佳答案
是的,你可以做到。为什么你会这样做可能是个人喜好。需要注意以下几点:
Docker-compose 将为所有服务生成一个默认网络,以便它们可以相互连接。当您像 docker-compose -f file1.yaml -f file2.yaml up 那样启动服务时,docker-compose 将合并 yaml 并创建一个名为 folderName_default
的网络。我还没有测试过它,但是将 yaml 放在不同的文件夹中可能意味着您必须指定一个自定义网络,并将该网络用于您的服务。您还可以单独启动服务,然后也是一样:如果它们位于同一文件夹中,那么应该可以工作。
如果您在 yaml 中使用 depends_on
键,则依赖的服务及其依赖的服务都应在同一个 yaml 文件中指定,或者您必须使用 启动它们docker-compose -f file1.yaml -f file2.yaml up
方式,因此它们将被合并。
另外,顺便说一句,可以使用 env 文件作为环境变量。这对于处理多个环境和/或长变量列表非常有用:
version: '3.6'
services:
inboxingester:
build:
context: ${INGESTER_CONTEXT}
dockerfile: Dockerfile
args:
BASE_IMAGE: ${INGESTER_APP_BASE_IMAGE}
artifactid: ${ingester_artifactid}
java_options: ${java_options} ${REMOTE_DEBUG}
image: ${INGESTER_IMAGE}
ports:
- "40500:40500"
env_file:
- ./env/database-vars
- ./env/some-other-vars
另请参阅documentation
关于docker - 如何将单个 docker-compose yml 文件拆分为多个 yml 文件,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/65805936/
我正在使用以下dockerfile: FROM ubuntu:14.04 MAINTAINER xxx xxx # SSH RUN apt-get update && apt-get install
我运行了docker-compose build celery,(经过数小时的尝试,我的连接不良)成功了。 app Dockerfile的前80%是相同的,但不会重复使用缓存。从我可以浏览的内容来看,
我可以使用以下命令成功创建 Docker 注册表 v2 服务:docker service create 然后我使用 docker Push 将一些图像推送到该服务。 当我通过 curl localh
我正在尝试使用 gitlab 构建 CI,我从 docker 的 docker 镜像开始,我的前端存储库没有任何问题,但现在使用相同的 gitlab-ci 配置文件,我有此守护程序错误。 这是构建的输
用例: 我们在 Jenkins 中有几个“发布作业”build 和 push 应用程序的 Docker 镜像到 docker registry,更新各种文件中的项目版本,最后将发布标签推送到相应的 G
当我尝试构建我的 docker 文件时,docker 返回以下错误: [+] Building 0.0s (1/2)
docker-in-docker 的作者在此博客中建议不要将此图像用于 CI 目的: jpetazzo/Using Docker-in-Docker for your CI or testing en
我创建了一个 Dockerfile 来在 Docker 中运行 Docker: FROM ubuntu:16.04 RUN apt-get update && \ apt-get in
我尝试为 Docker 镜像定位一个特定标签。我怎样才能在命令行上做到这一点?我想避免下载所有图像,然后删除不需要的图像。 在 Ubuntu 官方版本中,https://registry.hub.do
我正在尝试在docker中运行docker。唯一的目的是实验性的,我绝不尝试实现任何功能,我只想检查docker从另一个docker运行时的性能。 我通过Mac上的boot2docker启动docke
docker-compose.yml version: "3" services: daggr: image: "docker.pvt.com/test/daggr:stable"
我有一个非常具体的开发环境用例。在一些代码中,我启动了一个容器来抓取页面并检索在容器中运行的服务(Gitlab)的 token 。 现在,我希望 Dockerize 运行它的代码。具体来说,类似: o
之前已经问过这个问题,但我不确定当时是否可以使用docker-compose文件完成docker堆栈部署。 由于最新版本支持使用compose将服务部署到堆栈,因此,我无法理解dab文件的值。 我检查
我在一次采访中被问到这个问题,但无法回答。也没有找到任何相关信息。 最佳答案 正如 Docker 文档中所述,Docker 注册表是: [...] a hosted service containin
有没有一种方法可以将具有给定扩展名的所有文件复制到Docker中的主机?就像是 docker cp container_name:path/to/file/in/docker/*.png path/o
我的日志驱动程序设置为journald。使用日志记录驱动程序时,daemon.json文件中的日志级别配置会影响日志吗?使用docker logs 时仅会影响容器日志? 例如,docker和journ
我最近开始使用Docker + Celery。我还共享了full sample codes for this example on github,以下是其中的一些代码段,以帮助解释我的观点。 就上下文
运行docker build .命令后,尝试提交构建的镜像,但收到以下错误 Step 12 : CMD activator run ---> Using cache ---> efc82ff1ca
我们有docker-compose.yml,其中包含Kafka,zookeeper和schema registry的配置 当我们启动docker compose时,出现以下错误 docker-comp
我是Docker的新手。是否可以在Docker Hub外部建立Docker基本镜像存储库?假设将它们存储在您的云中,而不是拥有DH帐户?谢谢。 最佳答案 您可以根据需要托管自己的注册表。可以在Depl
我是一名优秀的程序员,十分优秀!