aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2018-11-19 13:20:56 -0600
committerbaude <bbaude@redhat.com>2018-11-20 09:49:34 -0600
commit690c52a113124efcedccb84e44198e7602f064ec (patch)
tree9a11d0ad045ae8f72354a80ede4068f0a9cbbeab /docs
parent4eecc8cf70728d733aa8d1c948093d9ae4a334df (diff)
downloadpodman-690c52a113124efcedccb84e44198e7602f064ec.tar.gz
podman-690c52a113124efcedccb84e44198e7602f064ec.tar.bz2
podman-690c52a113124efcedccb84e44198e7602f064ec.zip
Allow users to expose ports from the pod to the host
we need to allow users to expose ports to the host for the purposes of networking, like a webserver. the port exposure must be done at the time the pod is created. strictly speaking, the port exposure occurs on the infra container. Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/podman-pod-create.1.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/podman-pod-create.1.md b/docs/podman-pod-create.1.md
index 673ad9a8c..a63b12d73 100644
--- a/docs/podman-pod-create.1.md
+++ b/docs/podman-pod-create.1.md
@@ -51,6 +51,15 @@ Assign a name to the pod
Write the pod ID to the file
+**-p**, **--publish**=[]
+
+Publish a port or range of ports from the pod to the host
+
+Format: `ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort`
+Both hostPort and containerPort can be specified as a range of ports.
+When specifying ranges for both, the number of container ports in the range must match the number of host ports in the range.
+Use `podman port` to see the actual mapping: `podman port CONTAINER $CONTAINERPORT`
+
**--share**=""
A comma deliminated list of kernel namespaces to share. If none or "" is specified, no namespaces will be shared. The namespaces to choose from are ipc, net, pid, user, uts.