Star

docker swarm部署nebula集群问题

升级了docker,
data-storaged2:/data/storage挂载多个本机的卷该怎么解决?

    version: '3.6'
services:
  metad0:
    image: vesoft/nebula-metad:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --local_ip=192.168.8.191
      - --ws_ip=192.168.8.191
      - --port=45500
      - --data_path=/data/meta
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-191
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.191:11000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 11000
        published: 11000
        protocol: tcp
        mode: host
      - target: 11002
        published: 11002
        protocol: tcp
        mode: host
      - target: 45500
        published: 45500
        protocol: tcp
        mode: host
    volumes:
      - data-metad0:/data/meta
      - logs-metad0:/logs
    networks:
      - nebula-net

  metad1:
    image: vesoft/nebula-metad:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --local_ip=192.168.8.192
      - --ws_ip=192.168.8.192
      - --port=45500
      - --data_path=/data/meta
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-192
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.192:11000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 11000
        published: 11000
        protocol: tcp
        mode: host
      - target: 11002
        published: 11002
        protocol: tcp
        mode: host
      - target: 45500
        published: 45500
        protocol: tcp
        mode: host
    volumes:
      - data-metad1:/data/meta
      - logs-metad1:/logs
    networks:
      - nebula-net

  metad2:
    image: vesoft/nebula-metad:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --local_ip=192.168.8.193
      - --ws_ip=192.168.8.193
      - --port=45500
      - --data_path=/data/meta
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-193
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.193:11000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 11000
        published: 11000
        protocol: tcp
        mode: host
      - target: 11002
        published: 11002
        protocol: tcp
        mode: host
      - target: 45500
        published: 45500
        protocol: tcp
        mode: host
    volumes:
      - data-metad2:/data/meta
      - logs-metad2:/logs
    networks:
      - nebula-net

  storaged0:
    image: vesoft/nebula-storaged:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --local_ip=192.168.8.191
      - --ws_ip=192.168.8.191
      - --port=44500
      - --data_path=/data/storage
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-191
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.191:12000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 12000
        published: 12000
        protocol: tcp
        mode: host
      - target: 12002
        published: 12002
        protocol: tcp
        mode: host
    volumes:
      - data-storaged0:/data/storage
      - logs-storaged0:/logs
    networks:
      - nebula-net

  storaged1:
    image: vesoft/nebula-storaged:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --local_ip=192.168.8.192
      - --ws_ip=192.168.8.192
      - --port=44500
      - --data_path=/data/storage
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-192
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.192:12000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 12000
        published: 12000
        protocol: tcp
        mode: host
      - target: 12002
        published: 12004
        protocol: tcp
        mode: host
    volumes:
      - data-storaged1:/data/storage
      - logs-storaged1:/logs
    networks:
      - nebula-net

  storaged2:
    image: vesoft/nebula-storaged:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --local_ip=192.168.8.193
      - --ws_ip=192.168.8.193
      - --port=44500
      - --data_path=/data/storage
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-193
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.193:12000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 12000
        published: 12000
        protocol: tcp
        mode: host
      - target: 12002
        published: 12006
        protocol: tcp
        mode: host
    volumes:
      - data-storaged2:/data/storage
      - logs-storaged2:/logs
    networks:
      - nebula-net

  graphd:
    image: vesoft/nebula-graphd:v1.0.0
    env_file:
      - ./nebula.env
    command:
      - --meta_server_addrs=192.168.8.191:45500,192.168.8.192:45500,192.168.8.193:45500
      - --port=3699
      - --ws_ip=192.168.8.191
      - --log_dir=/logs
      - --v=0
      - --minloglevel=2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.hostname == node-191
    depends_on:
      - metad0
      - metad1
      - metad2
    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.8.191:13000/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 20s
    ports:
      - target: 3699
        published: 3699
        protocol: tcp
        mode: host
      - target: 13000
        published: 13000
        protocol: tcp
        mode: host
      - target: 13002
        published: 13002
        protocol: tcp
        mode: host
    volumes:
      - logs-graphd:/logs
    networks:
      - nebula-net

networks:
  nebula-net:
    external: true
    attachable: true
    name: host

volumes:
  data-metad0:
  logs-metad0:
  data-metad1:
  logs-metad1:
  data-metad2:
  logs-metad2:
  data-storaged0:
  logs-storaged0:
  data-storaged1:
  logs-storaged1:
  data-storaged2:
  logs-storaged2:
  logs-graphd:

如果constraints的hostname是对应的话,那看起来没啥问题

networks:
nebula-net:
external: true
attachable: true
name: host
这个语法3.1是不支持的,我查了官方文档,没有找到3.1该怎么写

hello

这个我知道,我想知道,机器有多个盘,怎么把多个盘挂载到容器里面。

docker volume create 没找到可以指定目录的选项,应该是不成了

我这边就搞了两个盘,一个盘较大用来存放数据的,配置docker时就把docker的root dir更改为该盘了

这里的网络主要是配置使用外部的 host 网络,这部分配置看文档应该是 2.0 开始就支持了 https://docs.docker.com/compose/compose-file/compose-file-v2/#external-1

1赞

这里的文档中可以通过指定 opt 选项的方式来配置你的磁盘路径,创建好 volume 后,在 docker-compose.yml 中配置 external 使用你创建的 volume 即可。

或者直接在 docker-compose.yml 中配置,看这里的文档:

2赞

我尝试过这种方式,报错,不过,先不管了,我升级了docker
networks:
outside:
external:
name: host

浙ICP备20010487号