diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-06-29 13:52:47 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-29 13:52:47 -0400 |
| commit | e0b93af70f1f1a183c99a350c6e588898b45c717 (patch) | |
| tree | 77271b38b5e61bff58ab3ba6f8e58b0ab48645cb /docs/source | |
| parent | c682ca3d35a3e4f9265e10dc9898cbe3ac3d35a2 (diff) | |
| parent | 3601b96600807214d74b9c77c614fa03bfae30a8 (diff) | |
| download | podman-e0b93af70f1f1a183c99a350c6e588898b45c717.tar.gz podman-e0b93af70f1f1a183c99a350c6e588898b45c717.tar.bz2 podman-e0b93af70f1f1a183c99a350c6e588898b45c717.zip | |
Merge pull request #6808 from mheon/allow_empty_hostport
Allow empty host port in --publish flag
Diffstat (limited to 'docs/source')
| -rw-r--r-- | docs/source/markdown/podman-create.1.md | 2 | ||||
| -rw-r--r-- | docs/source/markdown/podman-run.1.md | 3 |
2 files changed, 5 insertions, 0 deletions
diff --git a/docs/source/markdown/podman-create.1.md b/docs/source/markdown/podman-create.1.md index ded668f34..30ac54de2 100644 --- a/docs/source/markdown/podman-create.1.md +++ b/docs/source/markdown/podman-create.1.md @@ -626,6 +626,8 @@ When specifying ranges for both, the number of container ports in the range must (e.g., `podman run -p 1234-1236:1222-1224 --name thisWorks -t busybox` but not `podman run -p 1230-1236:1230-1240 --name RangeContainerPortsBiggerThanRangeHostPorts -t busybox`) With ip: `podman run -p 127.0.0.1:$HOSTPORT:$CONTAINERPORT --name CONTAINER -t someimage` +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` **--publish-all**, **-P**=*true|false* diff --git a/docs/source/markdown/podman-run.1.md b/docs/source/markdown/podman-run.1.md index 83971107f..2e2adbc7e 100644 --- a/docs/source/markdown/podman-run.1.md +++ b/docs/source/markdown/podman-run.1.md @@ -638,6 +638,9 @@ 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. +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**. **--publish-all**, **-P**=**true**|**false** |