Milvus
Zilliz
Home
  • Get Started
  • Home
  • Docs
  • Get Started

  • Install Milvus

  • Run Milvus Standalone

  • Docker (Linux)

Run Milvus in Docker (Linux)

This page illustrates how to launch a Milvus instance in Docker.

Prerequisites

Install Milvus in Docker

Milvus provides an installation script to install it as a docker container. The script is available in the Milvus repository. To install Milvus in Docker, just run

# Download the installation script
$ curl -sfL https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh -o standalone_embed.sh

# Start the Docker container
$ bash standalone_embed.sh start

What’s new in v2.6.0:

  • Streaming Node: Enhanced data processing capabilities
  • Woodpecker MQ: Improved message queue with reduced maintenance overhead, see Use Woodpecker for detail
  • Optimized Architecture: Consolidated components for better performance

Always download the latest script to ensure you get the most recent configurations and architecture improvements.

If you want to use Backup in standalone deployment mode, it is recommended to use the Docker Compose deployment method.

If you encounter any issues pulling the image, contact us at community@zilliz.com with details about the problem, and we’ll provide you with the necessary support.

After running the installation script:

  • A docker container named milvus has been started at port 19530.
  • An embed etcd is installed along with Milvus in the same container and serves at port 2379. Its configuration file is mapped to embedEtcd.yaml in the current folder.
  • To change the default Milvus configuration, add your settings to the user.yaml file in the current folder and then restart the service.
  • The Milvus data volume is mapped to volumes/milvus in the current folder.

You can access Milvus WebUI at http://127.0.0.1:9091/webui/ to learn more about the your Milvus instance. For details, refer to Milvus WebUI.

(Optional) Update Milvus configurations

You can modify the Milvus configurations in the user.yaml file in the current folder. For example, to change the proxy.healthCheckTimeout to 1000 ms, you can modify the file as follows:

cat << EOF > user.yaml
# Extra config to override default milvus.yaml
proxy:
  healthCheckTimeout: 1000 # ms, the interval that to do component healthy check
EOF

Then restart the service as follows:

$ bash standalone_embed.sh restart

For applicable configuration items, refer to System Configuration.

Upgrade Milvus

You can upgrade to the latest version of Milvus using the built-in upgrade command. This automatically downloads the latest configuration and Milvus image:

# Upgrade Milvus to the latest version
$ bash standalone_embed.sh upgrade

The upgrade command automatically:

  • Downloads the latest installation script with updated configurations
  • Pulls the latest Milvus Docker image
  • Restarts the container with the new version
  • Preserves your existing data and configurations

This is the recommended way to upgrade your Milvus standalone deployment.

Stop and delete Milvus

You can stop and delete this container as follows

# Stop Milvus
$ bash standalone_embed.sh stop

# Delete Milvus data
$ bash standalone_embed.sh delete

What’s next

Having installed Milvus in Docker, you can:

Office Hours

Milvus Office Hours

Get help with production deployment from Zilliz, the experts on Milvus.

Book a free 1:1 session

Try Managed Milvus for Free

Zilliz Cloud is hassle-free, powered by Milvus and 10x faster.

Get Started
Feedback

Was this page helpful?