opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-06-20 00:51:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #357 from edsantiago/vice-versa

Browse Source 
language: correct 'vice versa' in docs
This commit is contained in:
Daniel J Walsh
2018-02-19 12:51:25 -05:00
committed by GitHub
parent 07f15c2694 2cfe9cbf38
commit 32efbbdf8a
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/podman-create.1.md
View File

@ -512,10 +512,10 @@ The `Z` option tells podman to label the content with a private unshared label.
Only the current container can use a private volume. Only the current container can use a private volume.
By default bind mounted volumes are `private`. That means any mounts done By default bind mounted volumes are `private`. That means any mounts done
inside container will not be visible on host and vice-a-versa. One can change inside container will not be visible on host and vice versa. One can change
this behavior by specifying a volume mount propagation property. Making a this behavior by specifying a volume mount propagation property. Making a
volume `shared` mounts done under that volume inside container will be volume `shared` mounts done under that volume inside container will be
visible on host and vice-a-versa. Making a volume `slave` enables only one visible on host and vice versa. Making a volume `slave` enables only one
way mount propagation and that is mounts done on host under that volume way mount propagation and that is mounts done on host under that volume
will be visible inside container but not the other way around. will be visible inside container but not the other way around.

4
docs/podman-run.1.md
View File

@ -512,10 +512,10 @@ The `Z` option tells podman to label the content with a private unshared label.
Only the current container can use a private volume. Only the current container can use a private volume.
By default bind mounted volumes are `private`. That means any mounts done By default bind mounted volumes are `private`. That means any mounts done
inside container will not be visible on host and vice-a-versa. One can change inside container will not be visible on host and vice versa. One can change
this behavior by specifying a volume mount propagation property. Making a this behavior by specifying a volume mount propagation property. Making a
volume `shared` mounts done under that volume inside container will be volume `shared` mounts done under that volume inside container will be
visible on host and vice-a-versa. Making a volume `slave` enables only one visible on host and vice versa. Making a volume `slave` enables only one
way mount propagation and that is mounts done on host under that volume way mount propagation and that is mounts done on host under that volume
will be visible inside container but not the other way around. will be visible inside container but not the other way around.