From c1a35e1ba020447d2c78c1d27e1b439a54bfb15c Mon Sep 17 00:00:00 2001 From: Typing Turtle Date: Mon, 4 Oct 2021 05:50:21 -0400 Subject: [PATCH] Minor `read-only` clarification (#13521) * Minor `read-only` clarification ## Why It was not obvious to me that `ro` is the shorthand form of `readonly`. ## Description This adds a bit of text to explicitly state that `ro` is the shorthand form of `readonly` when using volumes * Update storage/volumes.md Co-authored-by: Sebastiaan van Stijn Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> Co-authored-by: Sebastiaan van Stijn --- storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/storage/volumes.md b/storage/volumes.md index b8c2f7763c..163b9e5079 100644 --- a/storage/volumes.md +++ b/storage/volumes.md @@ -72,7 +72,7 @@ If you need to specify volume driver options, you must use `--mount`. is mounted in the container. May be specified as `destination`, `dst`, or `target`. - The `readonly` option, if present, causes the bind mount to be [mounted into - the container as read-only](#use-a-read-only-volume). + the container as read-only](#use-a-read-only-volume). May be specified as `readonly` or `ro`. - The `volume-opt` option, which can be specified more than once, takes a key-value pair consisting of the option name and its value.