vesoft-inc/nebula-docker-compose

Issues

• 下载nebula-console版本再连接nebula后，出现 i/o timeout

  #115 opened 2 years ago by jiangpeng12345
  3

• failed to open connection, error: failed to open transport, error: dial tcp 172.19.0.10:9669: connect: connection refused during docker-compose up

  #160 opened 8 months ago by ice1x
  0

• Can names displayed after executing `docker-compose ps` be service names?

  #156 opened 10 months ago by abby-cyber
  0

• Something Wrong With vesoft/nebula-storaged:v3.6.0

  #155 opened a year ago by zhuyuemings
  2

• remove go panic information in nebula-console

  #110 opened 3 years ago by awsl-dbq
  3

• Console image `3.5.0` should be changed to `v3.5.0`

  #154 opened a year ago by abby-cyber
  0

• docker compose storage containers are always unhealthy

  #153 opened a year ago by recursively
  2

• A small bug in the latest released version 3.6.0(tar.gz)

  #152 opened a year ago by shubihu
  2

• nebula-docker-compose

  #141 opened a year ago by fxb392
  2

• Runing Nebula Graphdb on docker error Failed to read the directory "/data/meta/nebula" No such file or directory

  #150 opened 2 years ago by Jayuda
  2

• should change the version of console in 3.5.0 docker-compose yaml

  #147 opened 2 years ago by abby-cyber
  1

• Enable log forward to stderr/stdout

  #146 opened 2 years ago by wey-gu
  0

• Can we have a light version of docker-compose?

  #144 opened 2 years ago by artemkorsakov
  4

• revisit the health check URL for storaged when add-hosts is required(3.0+)

  #116 opened 3 years ago by wey-gu
  1

• do we actually need `cap_add`, if yes, we could document on why and if not, remove it.

  #135 opened 2 years ago by may11544
  3

• How to enable production level long run for log rotation

  #137 opened 2 years ago by wey-gu
  1

• nebula-conosle container failure in ARM docker env

  #134 opened 2 years ago by wey-gu
  1

• swarm need to be verified in nebulagraph v3

  #130 opened 2 years ago by wey-gu
  0

• Console exists right away - conn issue

  #126 opened 3 years ago by imrefazekas
  5

• run commond ”docker-compose up -d“ fail

  #117 opened 2 years ago by jiaxian-lin
  1

• Compatible with nerdctl

  #101 opened 3 years ago by wey-gu
  0

• docker-compose up -d

  #100 opened 2 years ago by zizihaier
  2

• 3机器集群返回了8行

  #46 opened 2 years ago by amber-moe
  2

• centos7 docker-compose up报错

  #40 opened 2 years ago by heshuguo
  1

• On macos, metad has no leader

  #34 opened 2 years ago by Shinji-IkariG
  1

• ERROR docker-compose up -d

  #25 opened 2 years ago by gocuntian
  2

• Use service name to replace ip to simplify network configuration

  #17 opened 5 years ago by yixinglu
  0

• create v3.0.2 branch

  #118 opened 3 years ago by wey-gu
  1

• Could not open the file: /sys/fs/cgroup/memory/memory.limit_in_bytes

  #111 opened 3 years ago by Jayuda
  2

• Whether it is normal for E_KEY_NOT_FOUND and Leader-count is zero ?

  #109 opened 3 years ago by awsl-dbq
  1

• unhealthy when use docker compose with v2.6.0 in M1 mac

  #108 opened 3 years ago by awsl-dbq
  8

• docker-compose up -d timeout

  #103 opened 3 years ago by CharleyXu
  2

• Website of this repo was linked to 1.0 nebula repo

  #92 opened 4 years ago by wey-gu
  2

• ram watermark bug not included in nightly build?

  #93 opened 4 years ago by wey-gu
  2

• add ansible

  #90 opened 4 years ago by cooper-lzy
  0

• Please use host name to replace fixed IP address in the docker-compose file.

  #48 opened 5 years ago by jessexi
  0

• provide doc with both start/stop and up/down(-v)

  #27 opened 5 years ago by whitewum
  0

• ERROR: unknown command line flag 'local_ip'

  #78 opened 4 years ago by codlin
  2

• Unstable connection and operation failed often

  #63 opened 4 years ago by ianhhhhhhhhe
  2

• 3699 occupied

  #61 opened 4 years ago by amber-moe
  0

• update listening ports

  #60 opened 4 years ago by oldLady344
  2

• 未设置密码账号，但是还是强制需要

  #59 opened 4 years ago by martixZero
  3

• id不支持负数

  #83 opened 4 years ago by nereus-east
  1

• unauthorized: incorrect username or password

  #82 opened 4 years ago by caalvinz
  1

• [ERROR (-8)]: Wrong vertex id type: 101

  #76 opened 4 years ago by xupengjun
  5

• Namespace parameter for charts may not be needed.

  #70 opened 4 years ago by matrixji
  1

• `docker run` command throws error

  #32 opened 5 years ago by back-to-eat
  2

• Same query returns different results

  #33 opened 5 years ago by back-to-eat
  1

• English suggestion

  #36 opened 5 years ago by amber-moe
  1