docs: correct read-only volume wording - #25614
Conversation
The read-only volume section incorrectly described the mount as a bind mount. Refer to the mounted data as a volume and remove the host propagation claim. Co-Authored-By: Codex <noreply@openai.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
area/engine
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The change correctly fixes the documentation to say that containers cannot write to the volume when it is mounted read-only, and removes the inaccurate claim about changes propagating back to the Docker host. The edit is accurate, well-scoped, and free of style-guide violations.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The change correctly replaces the inaccurate "bind mount" reference with "volume" and removes the unrelated claim that changes propagate back to the Docker host. The two new lines are accurate, concise, and consistent with the Docker documentation style guide — no hedge words, no redundant phrases, no marketing language.
No issues found.
3 participants
Summary
Correct the read-only volume section so it refers to writing to a volume rather than a bind mount. Remove the unrelated claim that changes propagate to the Docker host.
@netlify /engine/storage/volumes/
Preview the updated Volumes page
Closes #11159
Generated by Codex