zilliz/attu
Milvus management GUI
500K+
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.
Here are the steps to start a container for running Attu:
docker run -p 8000:3000 -e MILVUS_URL={milvus server IP}:19530 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.
Optional Environment Variables for Running Attu Docker
Parameter | Example | Required | Description |
---|---|---|---|
MILVUS_URL | 192.168.0.1:19530 | 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_URL
should 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:
Attu SSL Example
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
Custom Server Port Example
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 https://raw.githubusercontent.com/zilliztech/attu/main/attu-k8s-deploy.yaml
Make sure that the Attu pod can access the Milvus service. In the example provided this connects directly to my-release-milvus:19530
. 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:dev
yarn run build:release
Make 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!
❓ Do you have any questions or problems?
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 Discord 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 pull zilliz/attu