docs: 添加Windows下Docker启动慢的FAQ说明

[ai-ask]

• 添加Windows下Docker性能问题的原因分析
• 提供使用命名卷优化性能的解决方案
• 包含完整的docker-compose.yml配置示例
• 更新所有语言版本(zh/en/ja/zh-tw/zh-hk)

Summary by CodeRabbit

文档

• 新增 FAQ - 添加 Windows 环境下 Docker 启动速度优化指南，包括性能问题根本原因分析和使用命名卷的具体解决方案
• 多语言支持 - 英文、日文、繁体中文（香港/台湾）和简体中文文档均已同步更新

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

@develop-chen is attempting to deploy a commit to the deathsatan's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

概述

在多个语言版本的 FAQ 文档中新增关于 Windows 下 Docker 启动缓慢的问题解答。内容包括原因分析、解决方案、以及使用命名卷的 Docker Compose 配置示例，帮助用户优化跨文件系统 I/O 性能。

变更详情

群组 / 文件	变更摘要
多语言 FAQ 文档更新 docs/en/faq/index.md, docs/ja/faq/index.md, docs/zh-hk/faq/index.md, docs/zh-tw/faq/index.md, docs/zh/faq/index.md	各文档新增 FAQ 段落说明 Windows 环境下 Docker 启动性能问题。涵盖：(1) 问题背景与根本原因分析；(2) 基于命名卷的解决方案；(3) docker-compose.yml 配置示例，针对 vendor_data 和 runtime_data 目录使用命名卷，源码目录有限挂载；(4) 配置说明与掛载策略阐述。现有内容（如 APP_DEBUG 设置）保留不变。

代码审查工作量估算

🎯 2 (简单) | ⏱️ ~10 分钟

诗歌

🐰 五份文档同时响，
兔子的速度如飞快！
Windows Docker 优化妙，
命名卷助力跨系统飞翔，
启动如风，性能闪亮✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	PR标题清晰准确地反映了主要变更内容，即添加Windows下Docker启动慢的FAQ说明，与所有修改文件的内容相符。
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netlify]

❌ Deploy Preview for super-cobbler-53ff65 failed. Why did it fail? →

Name	Link
🔨 Latest commit	bc60331
🔍 Latest deploy log	https://app.netlify.com/projects/super-cobbler-53ff65/deploys/695881daeb582400082768a2

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/en/faq/index.md (1)

71-78: 可选：优化Line 73的词语表达

根据LanguageTool的建议，可考虑减少措辞的冗余度：

-This is especially noticeable when mounting directories with a large number of small files
+This is especially noticeable when mounting directories with many small files

这是可选的文体优化，不影响文档的准确性和清晰度。

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b84c1a8 and bc60331.

📒 Files selected for processing (5)

• docs/en/faq/index.md
• docs/ja/faq/index.md
• docs/zh-hk/faq/index.md
• docs/zh-tw/faq/index.md
• docs/zh/faq/index.md

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: People-Sea
Repo: mineadmin/doc-v3 PR: 0
File: :0-0
Timestamp: 2025-08-11T15:28:39.641Z
Learning: 用户 People-Sea 指示在 mineadmin/doc-v3 仓库的 PR 审查中暂时不需要检查 markdown (.md) 文件的内容。

🪛 LanguageTool

docs/en/faq/index.md

[style] ~73-~73: To reduce wordiness, try specifying a number or using “many” or “numerous” instead.
Context: ...ticeable when mounting directories with a large number of small files (such as the vendor direc...

(LARGE_NUMBER_OF)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Redirect rules - super-cobbler-53ff65
• GitHub Check: Header rules - super-cobbler-53ff65
• GitHub Check: Pages changed - super-cobbler-53ff65

🔇 Additional comments (2)

docs/ja/faq/index.md (1)

65-116: 文档结构与格式符合要求

根据之前的learnings指示，本次审查不对markdown文档内容进行深入检查。该文件的新增FAQ section结构完整，包含原因分析、解决方案说明、配置示例和相关说明，与英文版本保持一致。

docs/en/faq/index.md (1)

65-116: 文档结构与格式符合要求

根据之前的learnings指示，本次审查不对markdown文档内容进行深入检查。该文件的新增FAQ section结构完整，与日文版本保持一致，包含原因分析、解决方案、配置示例和相关说明。