summaryrefslogtreecommitdiff
path: root/docs/podman.1.md
diff options
context:
space:
mode:
authorValentin Rothberg <vrothberg@suse.com>2018-08-27 13:35:40 +0200
committerAtomic Bot <atomic-devel@projectatomic.io>2018-08-27 13:00:51 +0000
commit90e93e66b0906e59efe3025d801a0e122bd4c42e (patch)
treee782715b8ba6380b60888fec944955bf5df626bb /docs/podman.1.md
parent3b91c5e0c5880e5c6d3f24cf395b5d7d7512b853 (diff)
downloadpodman-90e93e66b0906e59efe3025d801a0e122bd4c42e.tar.gz
podman-90e93e66b0906e59efe3025d801a0e122bd4c42e.tar.bz2
podman-90e93e66b0906e59efe3025d801a0e122bd4c42e.zip
docs: add containers-mounts.conf(5)
Add a containers-mounts.conf(5) manpage. The mounts.conf is used by other tools (e.g., CRI-O) as well. A dedicated manpage reduces redundancy. Signed-off-by: Valentin Rothberg <vrothberg@suse.com> Closes: #1350 Approved by: rhatdan
Diffstat (limited to 'docs/podman.1.md')
-rw-r--r--docs/podman.1.md14
1 files changed, 2 insertions, 12 deletions
diff --git a/docs/podman.1.md b/docs/podman.1.md
index 095ccf961..8b9621115 100644
--- a/docs/podman.1.md
+++ b/docs/podman.1.md
@@ -137,17 +137,7 @@ When Podman runs in rootless mode, the file `$HOME/.config/containers/storage.co
**mounts.conf** (`/usr/share/containers/mounts.conf` and optionally `/etc/containers/mounts.conf`)
-The mounts.conf files specify volume mount directories that are automatically mounted inside containers when executing the `podman run` or `podman start` commands. Container processes can then use this content. The volume mount content does not get committed to the final image if you do a `podman commit`.
-
-Usually these directories are used for passing secrets or credentials required by the package software to access remote package repositories.
-
-For example, a mounts.conf with the line "`/usr/share/rhel/secrets:/run/secrets`", the content of `/usr/share/rhel/secrets` directory is mounted on `/run/secrets` inside the container. This mountpoint allows Red Hat Enterprise Linux subscriptions from the host to be used within the container.
-
-The format of the mounts.conf is the volume format /SRC:/DEST, one mount per line. Users can create an `/etc/containers/mounts.conf`, to specify their own special volumes to mount in the container. Podman by default reads /usr/share/containers/mounts.conf and the /etc/containers/mounts.conf if it exists.
-
-Note this is not a volume mount. The content of the volumes is copied into container storage, not bind mounted directly from the host.
-
-When Podman runs in rootless mode, the file `$HOME/.config/containers/mounts.conf` is also used.
+The mounts.conf files specify volume mount directories that are automatically mounted inside containers when executing the `podman run` or `podman start` commands. When Podman runs in rootless mode, the file `$HOME/.config/containers/mounts.conf` is also used. Please refer to containers-mounts.conf(5) for further details.
**hook JSON** (`/usr/share/containers/oci/hooks.d/*.json`)
@@ -191,7 +181,7 @@ Currently it is not possible to create a network device, so rootless containers
then only the loopback device will be available.
## SEE ALSO
-`oci-hooks(5)`, `containers-registries.conf(5)`, `containers-storage.conf(5)`, `crio(8)`
+`oci-hooks(5)`, `containers-mounts.conf(5)`, `containers-registries.conf(5)`, `containers-storage.conf(5)`, `crio(8)`
## HISTORY
Dec 2016, Originally compiled by Dan Walsh <dwalsh@redhat.com>