summaryrefslogtreecommitdiff
path: root/Dockerfile
diff options
context:
space:
mode:
authorMatthew Heon <mheon@redhat.com>2020-08-03 13:33:08 -0400
committerMatthew Heon <mheon@redhat.com>2020-08-03 14:32:16 -0400
commit7bedff96356eb1a4c14a0c86b41a70a8d4f41950 (patch)
treee4726cd3209526a9817c495a3765e7a5e706f494 /Dockerfile
parent1709335cf04e947117d4ae4dca72f24f4095511b (diff)
downloadpodman-7bedff96356eb1a4c14a0c86b41a70a8d4f41950.tar.gz
podman-7bedff96356eb1a4c14a0c86b41a70a8d4f41950.tar.bz2
podman-7bedff96356eb1a4c14a0c86b41a70a8d4f41950.zip
Do not set host IP on ports when 0.0.0.0 requested
Docker and CNI have very different ideas of what 0.0.0.0 means. Docker takes it to be 0.0.0.0/0 - that is, bind to every IPv4 address on the host. CNI (and, thus, root Podman) take it to mean the literal IP 0.0.0.0. Instead, CNI interprets the empty string ("") as "bind to all IPs". We could ask CNI to change, but given this is established behavior, that's unlikely. Instead, let's just catch 0.0.0.0 and turn it into "" when we parse ports. Fixes #7014 Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'Dockerfile')
0 files changed, 0 insertions, 0 deletions