Merge pull request #28163 from ysinghc/docs-publishport-protocol

docs(podman-systemd.unit.5.md): document protocol support for PublishPort  Fixes: #28146
This commit is contained in:
Matt Heon
2026-02-28 20:10:12 -05:00
committed by GitHub

View File

@@ -805,7 +805,8 @@ Exposes a port, or a range of ports (e.g. `50-59`), from the container to the ho
to the Podman `--publish` option. The format is similar to the Podman options, which is of
the form `ip:hostPort:containerPort`, `ip::containerPort`, `hostPort:containerPort` or
`containerPort`, where the number of host and container ports must be the same (in the case
of a range).
of a range). The protocol can be provided at the end, e.g., `hostPort:containerPort/tcp`.
Valid protocols are `tcp` and `udp`; the `sctp` protocol is supported only for rootful containers.
If the IP is set to 0.0.0.0 or not set at all, the port is bound on all IPv4 addresses on
the host; use [::] for IPv6.
@@ -1193,7 +1194,8 @@ Exposes a port, or a range of ports (e.g. `50-59`), from the pod to the host. Eq
to the Podman `--publish` option. The format is similar to the Podman options, which is of
the form `ip:hostPort:containerPort`, `ip::containerPort`, `hostPort:containerPort` or
`containerPort`, where the number of host and container ports must be the same (in the case
of a range).
of a range). The protocol can be provided at the end, e.g., `hostPort:containerPort/tcp`.
Valid protocols are `tcp` and `udp`; the `sctp` protocol is supported only for rootful containers.
If the IP is set to 0.0.0.0 or not set at all, the port is bound on all IPv4 addresses on
the host; use [::] for IPv6.
@@ -1380,7 +1382,8 @@ Exposes a port, or a range of ports (e.g. `50-59`), from the container to the ho
to the `podman kube play`'s `--publish` option. The format is similar to the Podman options, which is of
the form `ip:hostPort:containerPort`, `ip::containerPort`, `hostPort:containerPort` or
`containerPort`, where the number of host and container ports must be the same (in the case
of a range).
of a range). The protocol can be provided at the end, e.g., `hostPort:containerPort/tcp`.
Valid protocols are `tcp` and `udp`; the `sctp` protocol is supported only for rootful containers.
If the IP is set to 0.0.0.0 or not set at all, the port is bound on all IPv4 addresses on
the host; use [::] for IPv6.