docs: improve Docker notice with setup steps and example command#1259
docs: improve Docker notice with setup steps and example command#1259lin-bot23 wants to merge 3 commits into
Conversation
|
Warning Review limit reached
Next review available in: 23 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChangesDocker notice guidance
Possibly related PRs
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@snippets/install/docker-notice.mdx`:
- Around line 11-16: Update the Docker example in the installation notice to use
container volume paths specific to the documented community image, or clearly
instruct users to replace /ComfyUI/models and /ComfyUI/output with the paths
required by their selected image. Ensure the example’s mounts target directories
the named image actually uses.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 9f3b3b55-8630-4716-b5c4-fafef2ebf14f
📒 Files selected for processing (1)
snippets/install/docker-notice.mdx
…07-14-docker-notice-improvement
Summary
Multiple users asked about Docker installation on the docs homepage and installation pages. The existing Docker notice was too vague ('search Docker Hub') and did not provide actionable guidance. This update adds specific search terms, common setup steps (port mapping, volume mounts), and a Docker run command example.
Changes
Source
Mintlify AI Assistant analytics data (2026-07-14)
Checklist