summaryrefslogtreecommitdiff
path: root/docs/podman-run.1.md
diff options
context:
space:
mode:
authorCleber Rosa <crosa@redhat.com>2019-03-20 17:10:07 -0400
committerCleber Rosa <crosa@redhat.com>2019-03-20 17:10:07 -0400
commite936b1da5fa7ac0c656463c6d05e3af6e70c1111 (patch)
tree2b90d33b813be08e5a7b851de467cc2eeceba309 /docs/podman-run.1.md
parenta7098485969095197059fe27f3d636a689f642fd (diff)
downloadpodman-e936b1da5fa7ac0c656463c6d05e3af6e70c1111.tar.gz
podman-e936b1da5fa7ac0c656463c6d05e3af6e70c1111.tar.bz2
podman-e936b1da5fa7ac0c656463c6d05e3af6e70c1111.zip
docs/podman-run.1.md: remove extra whitespace in --read-only
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Diffstat (limited to 'docs/podman-run.1.md')
-rw-r--r--docs/podman-run.1.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/podman-run.1.md b/docs/podman-run.1.md
index cf385717e..b8b3d51f0 100644
--- a/docs/podman-run.1.md
+++ b/docs/podman-run.1.md
@@ -889,7 +889,7 @@ During container image development, containers often need to write to the image
content. Installing packages into /usr, for example. In production,
applications seldom need to write to the image. Container applications write
to volumes if they need to write to file systems at all. Applications can be
-made more secure by running them in read-only mode using the - -read-only switch.
+made more secure by running them in read-only mode using the --read-only switch.
This protects the containers image from modification. Read only containers may
still need to write temporary data. The best way to handle this is to mount
tmpfs directories on /run and /tmp.