Merge pull request #19976 from plettich/patch-1

[CI:DOCS] Fix some spelling and formatting  in volume options
This commit is contained in:
OpenShift Merge Robot 2023-09-14 17:49:43 +02:00 committed by GitHub
commit 3984b45b42
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions

View File

@ -62,7 +62,7 @@ and GID on the host.
The `:U` suffix tells Podman to use the correct host UID and GID based on the The `:U` suffix tells Podman to use the correct host UID and GID based on the
UID and GID within the <<container|pod>>, to change recursively the owner and UID and GID within the <<container|pod>>, to change recursively the owner and
group of the source volume. Chowning walks the file system under the volume and group of the source volume. Chowning walks the file system under the volume and
changes the UID/GID on each file, it the volume has thousands of inodes, this changes the UID/GID on each file. If the volume has thousands of inodes, this
process takes a long time, delaying the start of the <<container|pod>>. process takes a long time, delaying the start of the <<container|pod>>.
**Warning** use with caution since this modifies the host filesystem. **Warning** use with caution since this modifies the host filesystem.
@ -119,9 +119,8 @@ content, any changes from previous <<container|pod>> executions no longer exist.
One use case of the overlay mount is sharing the package cache from the One use case of the overlay mount is sharing the package cache from the
host into the container to allow speeding up builds. host into the container to allow speeding up builds.
Note: Note: The `O` flag conflicts with other options listed above.
- The `O` flag conflicts with other options listed above.
Content mounted into the container is labeled with the private label. Content mounted into the container is labeled with the private label.
On SELinux systems, labels in the source directory must be readable On SELinux systems, labels in the source directory must be readable
by the <<|pod infra>> container label. Usually containers can read/execute `container_share_t` by the <<|pod infra>> container label. Usually containers can read/execute `container_share_t`