summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2019-03-21 07:00:06 -0700
committerGitHub <noreply@github.com>2019-03-21 07:00:06 -0700
commitb83d05722f0233e7b0929602da1b4ebf3fc47dce (patch)
tree4aef66edd8fc16e10675f4fb8665ccb4958ee500
parent97b966b851dda998e44c0722f10655bd4b911434 (diff)
parente936b1da5fa7ac0c656463c6d05e3af6e70c1111 (diff)
downloadpodman-b83d05722f0233e7b0929602da1b4ebf3fc47dce.tar.gz
podman-b83d05722f0233e7b0929602da1b4ebf3fc47dce.tar.bz2
podman-b83d05722f0233e7b0929602da1b4ebf3fc47dce.zip
Merge pull request #2727 from clebergnu/podman_run_1_readonly
docs/podman-run.1.md: remove extra whitespace in --read-only
-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.