如何将单个 docker-compose yml 文件拆分为多个 yml 文件

问题描述 投票：0回答：2

我需要将单个 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

我已将其分成两个文件

  1. DB yml
  2. 摄取yml

我已将所有数据库相关服务复制到数据库 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 docker-compose
2个回答
6
投票

是的，你可以做到。为什么你会这样做可能是个人喜好。需要注意以下几点：

网络

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

另请参阅文档

0
投票

之前的答案现在有点过时了。较新版本的 docker compose 支持 

extend
/
include
关键字，可用于更好地在单独的文件中组织服务。

您可以在这里找到相关的 docker compose 文档。更多信息可以在 compose 规范中找到。

最新问题
© www.soinside.com 2019 - 2024. All rights reserved.