Release new docs to preview

Author: Milvus-doc-bot

v3.0.x/site/en/getstarted/run-milvus-docker/install_standalone-binary.md

@@ -17,7 +17,7 @@ This page illustrates how to install Milvus standalone with a pre-built RPM/DEB
 
 ## Download the RPM/DEB Package
 
-You can download the RPM/DEB package according to your system architecture from the [Milvus Releases page](https://github.com/milvus-io/milvus/releases/tag/v3.0-beta).
+You can download the RPM/DEB package according to your system architecture from the [Milvus Releases page](https://github.com/milvus-io/milvus/releases/tag/v2.6.9).
 
 - For x86_64/amd64, download the **milvus_2.6.9-1_amd64.deb** or **milvus_2.6.9-1_amd64.rpm** package.
 - For ARM64, download the **milvus_2.6.9-1_arm64.deb** or **milvus_2.6.9-1_arm64.rpm** package.
@@ -74,6 +74,12 @@ If Milvus is running successfully, you should see the following output:
 
 You can find the Milvus binary at `/usr/bin/milvus`, the systemd service file at `/lib/systemd/system/milvus.service`, and the dependencies at `/usr/lib/milvus/`.
 
+<div class="alert note">
+
+By default, Milvus Standalone runs **Woodpecker** (local filesystem) as its message queue with embedded etcd, so no external messaging or metadata service is required. See [Woodpecker](woodpecker.md).
+
+</div>
+
 ## (Optional) Update Milvus configurations
 
 You can modify the Milvus configurations in the `/etc/milvus/configs/milvus.yaml` file. For example, to change the `proxy.healthCheckTimeout` to `1000` ms, you can search for the target parameter and modify accordingly. For applicable configuration items, refer to [System Configuration](system_configuration.md).

v3.0.x/site/en/getstarted/run-milvus-docker/install_standalone-docker.md

@@ -33,7 +33,7 @@ $ bash standalone_embed.sh start
 
 **What's new in v3.0-beta:**
 - **Streaming Node**: Enhanced data processing capabilities
-- **Woodpecker MQ**: Improved message queue with reduced maintenance overhead, see [Use Woodpecker](use-woodpecker.md) for detail
+- **Woodpecker MQ (default)**: This Docker deployment runs Woodpecker as the message queue with the **local filesystem** as its WAL backend, so no external message-queue service is required. See [Woodpecker](woodpecker.md).
 - **Optimized Architecture**: Consolidated components for better performance
 
 Always download the latest script to ensure you get the most recent configurations and architecture improvements.
@@ -46,7 +46,7 @@ If you encounter any issues pulling the image, contact us at <a href="mailto:com
 
 After running the installation script:
 
-- A docker container named milvus has been started at port **19530**.
+- A docker container named milvus-standalone 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.
@@ -106,6 +106,14 @@ $ bash standalone_embed.sh stop
 $ bash standalone_embed.sh delete
 ```
 
+## Optional dependencies
+
+By default this deployment runs **Woodpecker** (local-filesystem WAL) as the message queue and an **embedded etcd** for metadata — nothing else to install. To use a different message queue or connect external object storage / metadata, see:
+
+- Message queue: [Woodpecker](woodpecker.md) (default) · [Pulsar](mq_pulsar.md) · [Kafka](mq_kafka.md) · [RocksMQ](mq_rocksmq.md)
+- Object storage: [MinIO](deploy_s3.md) (default) · [AWS S3](deploy_s3.md) · [Azure Blob](abs.md) · [GCP Cloud Storage](gcs.md) · [Aliyun OSS](deploy_s3.md) · [Tencent COS](deploy_s3.md) · [Huawei OBS](deploy_s3.md) · [S3-compatible](deploy_s3.md)
+- Metadata: [etcd](deploy_etcd.md)
+
 ## What's next
 
 Having installed Milvus in Docker, you can:

v3.0.x/site/en/getstarted/run-milvus-docker/install_standalone-windows.md

@@ -3,11 +3,13 @@ id: install_standalone-windows.md
 label: Docker
 related_key: Docker
 summary: Learn how to install Milvus standalone with Docker Desktop for Windows.
-title: Run Milvus in Docker (Linux)
+title: Run Milvus in Docker (Windows)
 ---
 
 # Run Milvus in Docker (Windows)
 
+> By default, this deployment runs **Woodpecker** (local filesystem) as its message queue, so no external message-queue service is required. See [Woodpecker](woodpecker.md).
+
 This page demonstrates how to run Milvus on Windows using Docker Desktop for Windows.​
 
 ## Prerequisites​
@@ -109,7 +111,7 @@ If you prefer to start Milvus using Linux commands and shell scripts on Windows,
     Stop successfully.​
     ​
     # Delete Milvus data​
-    $ bash standalone_embed.sh stop​
+    $ bash standalone_embed.sh delete​
     Delete Milvus container successfully.​
     Delete successfully.​
 
@@ -141,7 +143,7 @@ Once you have installed Docker Desktop on Microsoft Windows, you can access the
 
     - The **milvus-etcd** container does not expose any ports to the host and maps its data to **volumes/etcd** in the current folder.​
 
-    - The **milvus-minio** container serves ports **9090** and **9091** locally with the default authentication credentials and maps its data to **volumes/minio** in the current folder.​
+    - The **milvus-minio** container serves ports **9000** and **9001** locally with the default authentication credentials and maps its data to **volumes/minio** in the current folder.​
 
     - The **milvus-standalone** container serves ports **19530** locally with the default settings and maps its data to **volumes/milvus** in the current folder.​
 

v3.0.x/site/en/getstarted/run-milvus-docker/prerequisite-docker.md

@@ -32,7 +32,8 @@ The following dependencies will be obtained and configured automatically when Mi
 | -------- | ----------------------------- | ---- |
 | etcd     | 3.5.0                         |  See [additional disk requirements](#Additional-disk-requirements). |
 | MinIO    |  RELEASE.2024-12-18T13-15-44Z | |
-| Pulsar   | 2.8.2                         | |
+| Woodpecker | Bundled with Milvus | Default message queue (embedded); no separate service to install. |
+| Pulsar   | 2.8.2                         | Optional — only if you switch the message queue to Pulsar; not installed by default. |
 
 ### Additional disk requirements