diff options
author | Ed Santiago <santiago@redhat.com> | 2022-09-12 15:35:28 -0600 |
---|---|---|
committer | Ed Santiago <santiago@redhat.com> | 2022-09-13 09:02:34 -0600 |
commit | d4a0003122f94229723a9139db7da90600170dc3 (patch) | |
tree | dfce3755c7997fbb521adb4df42f66ade1455390 /docs/source/markdown/podman-run.1.md.in | |
parent | 4ff5bd854243a5931ea0dddb8254b161462ad0b6 (diff) | |
download | podman-d4a0003122f94229723a9139db7da90600170dc3.tar.gz podman-d4a0003122f94229723a9139db7da90600170dc3.tar.bz2 podman-d4a0003122f94229723a9139db7da90600170dc3.zip |
Man pages: Refactor common options: --publish
Almost identical between podman-create, run, and pod-create.
The "Notes" are different, so I left those duplicated between
podman-create and run, and left the different one in pod-create.
podman-container-restore also has --publish but it's unrelated.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-run.1.md.in')
-rw-r--r-- | docs/source/markdown/podman-run.1.md.in | 20 |
1 files changed, 1 insertions, 19 deletions
diff --git a/docs/source/markdown/podman-run.1.md.in b/docs/source/markdown/podman-run.1.md.in index fb421a4c3..a84584072 100644 --- a/docs/source/markdown/podman-run.1.md.in +++ b/docs/source/markdown/podman-run.1.md.in @@ -380,25 +380,7 @@ The total FDs will be 3+N. (This option is not available with the remote Podman @@option privileged -#### **--publish**, **-p**=*[[ip:][hostPort]:]containerPort[/protocol]* - -Publish a container's port, or range of ports, to the host. - -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. - -If host IP is set to 0.0.0.0 or not set at all, the port will be bound on all IPs on the host. - -By default, Podman will publish TCP ports. To publish a UDP port instead, give -`udp` as protocol. To publish both TCP and UDP ports, set `--publish` twice, -with `tcp`, and `udp` as protocols respectively. Rootful containers can also -publish ports using the `sctp` protocol. - -Host port does not have to be specified (e.g. `podman run -p 127.0.0.1::80`). -If it is not, the container port will be randomly assigned a port on the host. - -Use **podman port** to see the actual mapping: `podman port $CONTAINER $CONTAINERPORT`. +@@option publish **Note:** If a container will be run within a pod, it is not necessary to publish the port for the containers in the pod. The port must only be published by the pod itself. Pod network |