[Bug]: standalone use from Dockerfile

[Victordeleusse]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: 2.2.9
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Running an image on a standalone mode

FROM openshift.artifactory.mycloud.intranatixis.com/milvusdb/milvus:v2.2.9

ENV MILVUS_MODE=standalone

EXPOSE 19530 9091

CMD ["milvus", "run", "standalone"]

I have tried to modify the .yaml in the configs file

# Related configuration of etcd, used to store Milvus metadata & service discovery.
etcd:
  # endpoints:
    # - localhost:2379
  rootPath: by-dev # The root path where data is stored in etcd
  metaSubPath: meta # metaRootPath = rootPath + '/' + metaSubPath
  kvSubPath: kv # kvRootPath = rootPath + '/' + kvSubPath
  log:
    # path is one of:
    #  - "default" as os.Stderr,
    #  - "stderr" as os.Stderr,
    #  - "stdout" as os.Stdout,
    #  - file path to append server logs to.
    # please adjust in embedded Milvus: /tmp/milvus/logs/etcd.log
    path: stdout
    level: info # Only supports debug, info, warn, error, panic, or fatal. Default 'info'.
  use:
    # please adjust in embedded Milvus: true
    embed: true # Whether to enable embedded Etcd (an in-process EtcdServer).
  data:
    # Embedded Etcd only.
    # please adjust in embedded Milvus: /tmp/milvus/etcdData/
    dir: default.etcd
  ssl:
    enabled: false # Whether to support ETCD secure connection mode
    tlsCert: /path/to/etcd-client.pem # path to your cert file
    tlsKey: /path/to/etcd-client-key.pem # path to your key file
    tlsCACert: /path/to/ca.pem # path to your CACert file
    # TLS min version
    # Optional values: 1.0, 1.1, 1.2, 1.3。
    # We recommend using version 1.2 and above
    tlsMinVersion: 1.3" to set embed to true and dealocate the endpoints

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

[2024/11/27 11:59:08.564 +00:00] [INFO] [sessionutil/session_util.go:202] ["Session try to connect to etcd"] {"level":"warn","ts":"2024-11-27T11:59:08.656Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0008f2c40/localhost:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\""} {"level":"warn","ts":"2024-11-27T11:59:08.757Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00122a000/localhost:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\""} [2024/11/27 11:59:09.057 +00:00] [INFO] [sessionutil/session_util.go:202] ["Session try to connect to etcd"]

{"level":"warn","ts":"2024-11-27T11:59:08.463Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0006c7180/localhost:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\""} [2024/11/27 11:59:08.463 +00:00] [ERROR] [config/manager.go:181] ["Get configuration by items failed"] [error="context deadline exceeded"] [stack="github.com/milvus-io/milvus/internal/config.(*Manager).pullSourceConfigs\n\t/go/src/github.com/milvus-io/milvus/internal/config/manager.go:181\ngithub.com/milvus-io/milvus/internal/config.(*Manager).AddSource\n\t/go/src/github.com/milvus-io/milvus/internal/config/manager.go:163\ngithub.com/milvus-io/milvus/internal/config.Init\n\t/go/src/github.com/milvus-io/milvus/internal/config/config.go:48\ngithub.com/milvus-io/milvus/internal/util/paramtable.(*BaseTable).initConfigsFromRemote\n\t/go/src/github.com/milvus-io/milvus/internal/util/paramtable/base_table.go:169\ngithub.com/milvus-io/milvus/internal/util/paramtable.(*BaseTable).Init\n\t/go/src/github.com/milvus-io/milvus/internal/util/paramtable/base_table.go:119\ngithub.com/milvus-io/milvus/internal/util/paramtable.(*ServiceParam).Init\n\t/go/src/github.com/milvus-io/milvus/internal/util/paramtable/service_param.go:57\ngithub.com/milvus-io/milvus/internal/util/paramtable.(*ComponentParam).Init\n\t/go/src/github.com/milvus-io/milvus/internal/util/paramtable/component_param.go:86\ngithub.com/milvus-io/milvus/internal/util/paramtable.(*ComponentParam).InitOnce.func1\n\t/go/src/github.com/milvus-io/milvus/internal/util/paramtable/component_param.go:80\nsync.(*Once).doSlow\n\t/usr/local/go/src/sync/once.go:68\nsync.(*Once).Do\n\t/usr/local/go/src/sync/once.go:59\ngithub.com/milvus-io/milvus/internal/util/paramtable.(*ComponentParam).InitOnce\n\t/go/src/github.com/milvus-io/milvus/internal/util/paramtable/component_param.go:79\ngithub.com/milvus-io/milvus/cmd/roles.(*MilvusRoles).runDataCoord\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:191\ngithub.com/milvus-io/milvus/cmd/roles.(*MilvusRoles).Run\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:313\ngithub.com/milvus-io/milvus/cmd/milvus.(*run).execute\n\t/go/src/github.com/milvus-io/milvus/cmd/milvus/run.go:112\ngithub.com/milvus-io/milvus/cmd/milvus.RunMilvus\n\t/go/src/github.com/milvus-io/milvus/cmd/milvus/milvus.go:60\nmain.main\n\t/go/src/github.com/milvus-io/milvus/cmd/main.go:26\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"]

Anything else?

No response

[yanliang567]

@Victordeleusse please retry on latest milvus release v2.4.17 or v2.5.0-beta.
/unassign
/assign @Victordeleusse