Skip to content

Clarify volume mount wording in persist DB tutorial#25405

Open
devendrakushwah80 wants to merge 1 commit into
docker:mainfrom
devendrakushwah80:fix-persist-db-wording
Open

Clarify volume mount wording in persist DB tutorial#25405
devendrakushwah80 wants to merge 1 commit into
docker:mainfrom
devendrakushwah80:fix-persist-db-wording

Conversation

@devendrakushwah80

Copy link
Copy Markdown
Contributor

Description

Clarifies the wording in the "Persist the DB" workshop tutorial.

The volume is already created and named (todo-db) in step 1 using docker volume create. The previous wording in step 3 suggested that the volume was being named there, while the command actually uses the existing volume as the mount source.

This change updates the wording to make the workflow clearer and more technically accurate.

Related issues or tickets

Fixes #25404

Reviews

  • Technical review
  • Editorial review
  • Product review

@netlify

netlify Bot commented Jun 21, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 7a2bfcc
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6a37b79170e56400083ec8da
😎 Deploy Preview https://deploy-preview-25405--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added the area/get-started Relates to get started and onboarding docs label Jun 21, 2026
@craig-osterhout craig-osterhout added the status/review Pull requests that are ready for review label Jun 22, 2026
@craig-osterhout

Copy link
Copy Markdown
Contributor

/review

@docker-agent docker-agent left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

The wording change is technically accurate and clear. The previous text ("Give the volume a name") was misleading because the volume todo-db is already created in step 1. The new text ("Use the volume named todo-db") correctly reflects that the existing volume is being referenced as the mount source. No issues found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/get-started Relates to get started and onboarding docs status/review Pull requests that are ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation error in Part 4: Persist the DB

3 participants