Self-host Milvus with Levelrail
A cloud-native vector database built for billion-scale similarity search, run here as a single standalone node. Has no authentication, so reach it from other services in this project at milvus:19530, or attach a domain (it routes to port 19530 only) only behind Basic Auth. Not published on the host.
- Authormilvus-io
- LicenceApache-2.0
- Memory4 GiB
- Archarm64
- Services1
How to self-host Milvus
-
Pull the images
One image is pulled on your server.
Show images
milvusdb/milvus:v3.0.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 19530, 9091.
-
Fill in the secrets
4 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Milvus requirements
- Memory
- About 4 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 19530, 9091
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Milvus. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Milvus docs page.
Deploy Milvus your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Milvus from the CLI
levelrail-cli templates deploy milvus --name my-milvus Deploy Milvus with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/milvus/deploy Milvus configuration
Milvus services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| milvus | milvusdb/milvus:v3.0.2 | 19530, 9091 | milvus_data -> /var/lib/milvus |
Milvus environment variables
| Variable | Service | Value |
|---|---|---|
| COMMON_STORAGETYPE | milvus | Preset by the template |
| DEPLOY_MODE | milvus | Preset by the template |
| ETCD_DATA_DIR | milvus | Preset by the template |
| ETCD_USE_EMBED | milvus | Preset by the template |
Ports and volumes
- Ports
- 19530, 9091
- Volumes
- 1 named mount: milvus_data -> /var/lib/milvus
Milvus FAQ
How much memory does Milvus need?
The catalog lists about 4 GiB of memory for Milvus.
Does Milvus run on arm64?
For Milvus, an arm64 image is published; amd64 is image published.
What licence is Milvus under?
Milvus is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Milvus need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Milvus use?
Milvus listens on ports 19530 and 9091 inside the stack.
Where does Milvus keep its data?
In a named volume: milvus_data mounted at /var/lib/milvus.
Can I deploy Milvus on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Milvus, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image milvusdb/milvus:v3.0.2 is what you deploy there.