Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: milvus2.5.4版本通过docker-compose.yml启动,启动监控报错 #40033

Open
1 task done
feng555g opened this issue Feb 20, 2025 · 3 comments
Open
1 task done
Assignees
Labels
area/deployment any issues that related to deployment kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@feng555g
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

milvus2.5.4 standalone版本

Current Behavior

请问下,milvus2.5.4版本的docker-compose.yml下开启监控选项,为啥报错?是不是参数变了?之前milvus2.5.0版本都没有这个问题?
environment:
ETCD_ENDPOINTS: etcd:2379
MINIO_ADDRESS: minio:9000
METRIC_ENABLE: "true"
METRIC_PORT: "9091"

Expected Behavior

docker-compose up -d
Starting milvus-minio ... done
Starting milvus-etcd ... done
Recreating 0fdc490932c4_milvus-standalone ...

ERROR: for 0fdc490932c4_milvus-standalone 'ContainerConfig'

ERROR: for standalone 'ContainerConfig'

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

@feng555g feng555g added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 20, 2025
Copy link
Contributor

The title and description of this issue contains Chinese. Please use English to describe your issue.

Copy link

dosubot bot commented Feb 20, 2025

Hey @feng555g, I'm here to help you with any bugs, questions, and contributions you might have for Milvus 2.5.4. Let me know how I can assist you!

The error you're encountering with the ContainerConfig when enabling monitoring in Milvus 2.5.4 using docker-compose.yml might be related to changes in configuration or environment variables between versions 2.5.0 and 2.5.4.

Here are a few things to check:

  1. Environment Variables: Ensure that the environment variables METRIC_ENABLE and METRIC_PORT are correctly set. The default values for these in Milvus 2.5.4 are "false" for METRIC_ENABLE and "9091" for METRIC_PORT [1].

  2. Configuration Changes: Verify if there are any changes in the docker-compose.yml file between versions 2.5.0 and 2.5.4 that might affect the monitoring setup. Unfortunately, I don't have specific information on changes in the docker-compose.yml file between these versions.

  3. Dependencies and Requirements: Ensure that all dependencies and requirements for running Milvus 2.5.4 with monitoring enabled are met. This includes setting up Kafka, Etcd, and Prometheus correctly [2][3].

If the issue persists, consider checking the Milvus documentation or release notes for any additional changes or updates related to monitoring in version 2.5.4.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot dosubot bot added the area/deployment any issues that related to deployment label Feb 20, 2025
@yanliang567
Copy link
Contributor

I don't think we have changed anything here.
/assign @LoveEachDay
could you please help to double confirm
.unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/deployment any issues that related to deployment kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants