How to create milvus and write Docker compose to ensure port conflicts are avoided

[huangzong123]

There is already a milvus database started using Docker Compose on the server host. I need to start another milvus database. How can I write Docker Compose to ensure that both databases exist simultaneously and ports do not interfere with each other.

[yhmo]

1. make sure container_name is different
2. make sure networks name is different
3. make sure port 19530 is exposed to different ports

For example, start two milvus standalone with two docker-compose.yaml

• The first yaml

version: '3.5'

services:
  etcd:
    container_name: milvus-etcd-1
    image: quay.io/coreos/etcd:v3.5.5
    environment:
      - ETCD_AUTO_COMPACTION_MODE=revision
      - ETCD_AUTO_COMPACTION_RETENTION=1000
      - ETCD_QUOTA_BACKEND_BYTES=4294967296
      - ETCD_SNAPSHOT_COUNT=50000

    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/etcd:/etcd
    command: etcd -advertise-client-urls=http://127.0.0.1:2379 -listen-client-urls http://0.0.0.0:2379 --data-dir /etcd
    healthcheck:
      test: ["CMD", "etcdctl", "endpoint", "health"]
      interval: 30s
      timeout: 20s
      retries: 3

  minio:
    container_name: milvus-minio-1
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin

    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

  standalone:
    container_name: milvus-standalone-1
    image: milvusdb/milvus:v2.5.1
    command: ["milvus", "run", "standalone"]
    security_opt:
    - seccomp:unconfined
    environment:
      ETCD_ENDPOINTS: etcd:2379
      MINIO_ADDRESS: minio:9000
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]
      interval: 30s
      start_period: 90s
      timeout: 20s
      retries: 3
    ports:
      - "19530:19530"
      - "9091:9091"
    depends_on:
      - "etcd"
      - "minio"

networks:
  default:
    name: milvus_1

• The second yaml

version: '3.5'

services:
  etcd:
    container_name: milvus-etcd-2
    image: quay.io/coreos/etcd:v3.5.5
    environment:
      - ETCD_AUTO_COMPACTION_MODE=revision
      - ETCD_AUTO_COMPACTION_RETENTION=1000
      - ETCD_QUOTA_BACKEND_BYTES=4294967296
      - ETCD_SNAPSHOT_COUNT=50000
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/etcd:/etcd
    command: etcd -advertise-client-urls=http://127.0.0.1:2379 -listen-client-urls http://0.0.0.0:2379 --data-dir /etcd
    healthcheck:
      test: ["CMD", "etcdctl", "endpoint", "health"]
      interval: 30s
      timeout: 20s
      retries: 3

  minio:
    container_name: milvus-minio-2
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

  standalone:
    container_name: milvus-standalone-2
    image: milvusdb/milvus:v2.4.16
    command: ["milvus", "run", "standalone"]
    security_opt:
    - seccomp:unconfined
    environment:
      ETCD_ENDPOINTS: etcd:2379
      MINIO_ADDRESS: minio:9000
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]
      interval: 30s
      start_period: 90s
      timeout: 20s
      retries: 3
    ports:
      - "39530:19530"
      - "39091:9091"
    depends_on:
      - "etcd"
      - "minio"


networks:
  default:
    name: milvus_2

Connect to the milvus_1:
connections.connect(host='localhost', port=19530)

Connect to the milvus_2:
connections.connect(host='localhost', port=39530)

[huangzong123]

如果不仅是milvus-standalone，需要将etcd和minio也全部独立出来，均不共用其服务和端口，请问该如何调整，谢谢！

[yhmo]

这两个yaml文件里就是独立的etcd/minio，并没有共用

[huangzong123]

竟然可以共用端口吗，会不会存在什么干扰，另外里面的数据是混在一起的，还是各存各的

[yhmo]

两个yaml文件分别定义了自己的虚拟网络，容器在各自所属的虚拟网络中运行，虚拟网络之间互不干扰。

networks:
  default:
    name: milvus_1

networks:
  default:
    name: milvus_2

milvus_1把自己的19530端口暴露给宿主机的19530端口，所以你用sdk连接19530端口时是连接1号milvus

standalone:
    ports:
      - "19530:19530"

milvus_1把自己的19530端口暴露给宿主机的39530端口，所以你用sdk连接39530端口时是连接2号milvus

standalone:
    ports:
      - "39530:19530"

[huangzong123]

好的，了解了，我试试，感谢解惑