本站支持搜索的镜像仓库:Docker Hub、gcr.io、ghcr.io、quay.io、k8s.gcr.io、registry.gcr.io、elastic.co、mcr.microsoft.com

![typescript]([] ![downloads]([]
Attu is an all-in-one milvus administration tool. With Attu, you can dramatically reduce the cost of managing milvus.
Before you begin, make sure that you have Milvus installed on either Zilliz Cloud or your own server.
| Milvus Version | Recommended Attu Version |
|---|---|
| 2.5.x | v2.5.6 |
| 2.4.x | v2.4.12 |
| 2.3.x | v2.3.5 |
| 2.2.x | v2.2.8 |
| 2.1.x | v2.2.2 |
Here are the steps to start a container for running Attu:
docker run -p 8000:3000 -e MILVUS_URL={milvus server IP}:*** zilliz/attu:v2.4
Make sure that the Attu container can access the Milvus IP address. After starting the container, open your web browser and enter http://{ Attu IP }:8000 to view the Attu GUI.
| Parameter | Example | Required | Description |
|---|---|---|---|
| MILVUS_URL | 192.168.0.1:*** | false | Optional, Milvus server URL |
| ATTU_LOG_LEVEL | info | false | Optional, sets the log level for Attu |
| ROOT_CERT_PATH | /path/to/root/cert | false | Optional, path to the root certificate |
| PRIVATE_KEY_PATH | /path/to/private/key | false | Optional, path to the private key |
| CERT_CHAIN_PATH | /path/to/cert/chain | false | Optional, path to the certificate chain |
| SERVER_NAME | your_server_name | false | Optional, name of your server |
| SERVER_PORT | Server listen port | false | Optional, 3000 by default if unset |
Please note that the
MILVUS_URLshould be an address that the Attu Docker container can access. Therefore, "127.0.0.1" or "localhost" will not work.
To run the Docker container with these environment variables, use the following command:
docker run -p 8000:3000 \ -v /your-tls-file-path:/app/tls \ -e ATTU_LOG_LEVEL=info \ -e ROOT_CERT_PATH=/app/tls/ca.pem \ -e PRIVATE_KEY_PATH=/app/tls/client.key \ -e CERT_CHAIN_PATH=/app/tls/client.pem \ -e SERVER_NAME=your_server_name \ zilliz/attu:dev
This command lets you run the docker container with host networking, specifying a custom port for the server to listen on
docker run --network host \ -v /your-tls-file-path:/app/tls \ -e ATTU_LOG_LEVEL=info \ -e SERVER_NAME=your_server_name \ -e SERVER_PORT=8080 \ zilliz/attu:dev
Before you begin, make sure that you have Milvus installed and running within your K8's Cluster. Note that Attu only supports Milvus 2.x.
Here are the steps to start a container for running Attu:
kubectl apply -f [***]
Make sure that the Attu pod can access the Milvus service. In the example provided this connects directly to my-release-milvus:***. Change this based on the Milvus service name. A more flexible way to achieve this would be to introduce a ConfigMap. See this example for details.
If you prefer to use a desktop application, you can download the desktop version of Attu.
yarn run build:devyarn run build:releaseMake sure that the IP address of the Milvus server can be accessed from the Attu container. #161
| Data view | collection tree |
|---|---|
| create collection | vector search |
|---|---|
Thank you for your interest in contributing to Attu! Here's how you can build Attu locally to contribute code, test out the latest features, or try out an open PR:
cd server in the terminal.yarn install.yarn start.git checkout -b my-branch.cd client in the terminal.yarn install.yarn start.git checkout -b my-branch.We appreciate your contributions to Attu, regardless of size. Thanks for supporting the project!
If you encounter any bugs or want to request a new feature, please create a GitHub issue. It's important to check if someone else has already created an issue for the same problem before submitting a new one.
Here are some helpful resources to get you started with Milvus:
💬 Join our vibrant community on the Milvus *** where you can share your knowledge, ask questions and engage in meaningful conversations. It's not just about coding, it's about connecting with other like-minded individuals. Click the link below to join now!
免费版仅支持 Docker Hub 加速,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
免费版仅支持 docker.io;专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录方式配置轩辕镜像加速服务,包含7个详细步骤
在 Linux 系统上配置轩辕镜像源,支持主流发行版
在 Docker Desktop 中配置轩辕镜像加速,适用于桌面系统
在 Docker Compose 中使用轩辕镜像加速,支持容器编排
在 k8s 中配置 containerd 使用轩辕镜像加速
在宝塔面板中配置轩辕镜像加速,提升服务器管理效率
在 Synology 群晖NAS系统中配置轩辕镜像加速
在飞牛fnOS系统中配置轩辕镜像加速
在极空间NAS中配置轩辕镜像加速
在爱快ikuai系统中配置轩辕镜像加速
在绿联NAS系统中配置轩辕镜像加速
在威联通NAS系统中配置轩辕镜像加速
在 Podman 中配置轩辕镜像加速,支持多系统
配置轩辕镜像加速9大主流镜像仓库,包含详细配置步骤
无需登录即可使用轩辕镜像加速服务,更加便捷高效
需要其他帮助?请查看我们的 常见问题 或 官方QQ群: 13763429