diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2018-01-29 13:30:53 +0100 |
|---|---|---|
| committer | Atomic Bot <atomic-devel@projectatomic.io> | 2018-01-29 15:21:34 +0000 |
| commit | 099b5fb6f6fb1397afc664820239a904585ddd04 (patch) | |
| tree | ddc48f065990bcaf660e77124b4f3457be32eb85 /docs/podman-run.1.md | |
| parent | cc5a6a3cb1b6801a1dd81d983bd79d54df880b88 (diff) | |
| download | podman-099b5fb6f6fb1397afc664820239a904585ddd04.tar.gz podman-099b5fb6f6fb1397afc664820239a904585ddd04.tar.bz2 podman-099b5fb6f6fb1397afc664820239a904585ddd04.zip | |
Ran spell checker through all man pages
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Closes: #269
Approved by: TomSweeneyRedHat
Diffstat (limited to 'docs/podman-run.1.md')
| -rw-r--r-- | docs/podman-run.1.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/podman-run.1.md b/docs/podman-run.1.md index 8a36bf425..7290a5bd5 100644 --- a/docs/podman-run.1.md +++ b/docs/podman-run.1.md @@ -252,7 +252,7 @@ millions of trillions. **--link-local-ip**=[] Add one or more link-local IPv4/IPv6 addresses to the container's interface -**--log-driver**="*json-file*|*syslog*|*journald*|*gelf*|*fluentd*|*awslogs*|*splunk*|*etwlogs*|*gcplogs*|*none*" +**--log-driver**="*json-file*" Logging driver for the container. Default is defined by daemon `--log-driver` flag. **Warning**: the `podman logs` command works only for the `json-file` and `journald` logging drivers. @@ -349,7 +349,7 @@ This is because by default a container is not allowed to access any devices. A “privileged” container is given access to all devices. When the operator executes **podman run --privileged**, podman enables access -to all devices on the host as well as set turn off most of the security messurs +to all devices on the host as well as set turn off most of the security measures protecting the host from the container. **-p**, **--publish**=[] @@ -529,7 +529,7 @@ Use `df <source-dir>` to figure out the source mount and then use `findmnt -o TARGET,PROPAGATION <source-mount-dir>` to figure out propagation properties of source mount. If `findmnt` utility is not available, then one can look at mount entry for source mount point in `/proc/self/mountinfo`. Look -at `optional fields` and see if any propagaion properties are specified. +at `optional fields` and see if any propagation properties are specified. `shared:X` means mount is `shared`, `master:X` means mount is `slave` and if nothing is there that means mount is `private`. |