-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add bind-recursive
mount option
#4606
Conversation
Follow-up to PR 4316 Signed-off-by: Akihiro Suda <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4606 +/- ##
==========================================
- Coverage 59.71% 59.70% -0.01%
==========================================
Files 288 286 -2
Lines 24858 24855 -3
==========================================
- Hits 14843 14839 -4
Misses 9128 9128
- Partials 887 888 +1 |
/cc @dvdksn ptal (let me know if you want to do a zoom call to walk through these options!) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AkihiroSuda - these changes LGTM. I will make a follow-up with changes to the bind mount documentation in docker/docs (https://docs.docker.com/storage/bind-mounts/)
<li><<tt>enabled</tt>, <tt>true</tt> or <tt>1</tt>: Enables recursive bind-mount. | ||
Read-only mounts are made recursively read-only if kernel is v5.12 or later. | ||
Otherwise they are not made recursively read-only.</li> | ||
<li><<tt>disabled</tt>, <tt>false</tt> or <tt>0</tt>: Disables recursive bind-mount.</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened a PR for discussion to remove the boolean variants (motivation outlined in that PR);
Follow-up to
bind-recursive=<bool|string>
and deprecatebind-nonrecursive=<bool>
#4316