fix: clarified rprivate by adding spell out recursive private in volumes.md (#21711)

## Description

<!-- Tell us what you did and why -->
To avoid confusion of rprivate provided fix: clarified rprivate by
adding spell out recursive private in volumes.md

## Related issues or tickets
#21688

<!-- Related issues, pull requests, or Jira tickets --> 
#21688

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review

---------

Signed-off-by: Rashi Chaubal <12rashic@gmail.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
Rashi Chaubal 2025-02-05 14:49:29 +05:30 committed by GitHub
parent a99cd5a131
commit 6c679a648d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -56,7 +56,7 @@ If your container generates non-persistent state data, consider using a
increase the container's performance by avoiding writing into the container's
writable layer.
Volumes use `rprivate` bind propagation, and bind propagation isn't
Volumes use `rprivate` (recursive private) bind propagation, and bind propagation isn't
configurable for volumes.
## A volume's lifecycle