milvus: [Bug]: The default path of configDir

Is there an existing issue for this?

I have searched the existing issues

Environment

- Milvus version: 2.0.0-rc8
- Deployment mode(standalone or cluster): standalone
- OS(Ubuntu or CentOS): Ubuntu

Current Behavior

I compiled Milvus from source and then i run milvus binary file on another computer.

If i don’t set the environment variable MILVUSCONF, and there is no config file in the running path. The default configDir is the path where i complied Milvus.

Expected Behavior

I want to set the default configDir to be a fixed path, not the absolute path where the Milvus compiled.

Steps To Reproduce

No response

Anything else?

No response

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17 (11 by maintainers)

Most upvoted comments

You can try the following steps if you’re not familiar with docker:

download & install & start docker

docker pull milvusdb/milvus-env:amd64-ubuntu18.04-latest

docker run --name=milvus-env -d -v ${Change me to: the path to your milvus code base}:/data/milvus milvusdb/milvus-env:amd64-ubuntu18.04-latest sh -c 'while sleep 3600; do :; done'

docker exec -it milvus-env 'bash'

cd /data/milvus

now you can change the code & run the test with go test -run ^TestBateTable_ConfPath$ ./internal/util/metricsinfo

I followed the instructions, during starting a container, there is a problem with autouseradd: running as root is not permitted. I solved it by running docker run --name=milvus-envs -d -v ${my path}:/data/milvus -u "$(id -u):$(id -g)" milvusdb/milvus-env:amd64-ubuntu18.04-latest instead. Posted this in case someone encountered a similar problem.

SpikeWong on Dec 29, 2021