mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-29 03:37:54 +00:00
5e63372ffa
When multiple containers in a pod YAML specify the same hostPort, podman kube play previously accepted the YAML and started the containers, causing one of them to fail at runtime with a confusing bind() error. Add early validation in getPodPorts() to detect duplicate (hostIP, hostPort, protocol) tuples across containers and return a clear error message naming both conflicting containers. Fixes: https://github.com/podman-container-tools/podman/issues/26622 Signed-off-by: Miguel Álvarez <mialvare@redhat.com> |
||
|---|---|---|
| .. | ||
| generate | ||
| container_validate.go | ||
| namespaces.go | ||
| namespaces_test.go | ||
| pod_validate.go | ||
| podspecgen.go | ||
| resources_freebsd.go | ||
| resources_linux.go | ||
| specgen.go | ||
| specgen_local.go | ||
| specgen_remote.go | ||
| specgen_test.go | ||
| utils.go | ||
| utils_linux.go | ||
| volumes.go | ||
| volumes_linux_test.go | ||
| volumes_windows_test.go | ||
| winpath.go | ||
| winpath_linux.go | ||
| winpath_unsupported.go | ||
| winpath_windows.go | ||