Publishing a privileged port on specific IP address fails on Mac

Issue Description

Trying to bind a privileged container port to a host IP address fails:

❯ > podman run --rm -p 127.0.0.1:879:80 alpine echo 1
Error: preparing container 610b74d61baaee4bdf2b06c8d0e679dd059786c5ebc5eaf796338ba1872a984f for attach: something went wrong with the request: "listen tcp 127.0.0.1:879: bind: permission denied\n"

Leaving out the ip address or changing to an unprivileged port makes the command succeed:

❯ > podman run --rm -p 879:80 alpine echo 1
1

❯ > podman run --rm -p 127.0.0.1:1879:80 alpine echo 1
1

Steps to reproduce the issue

Steps to reproduce the issue

1. Install podman on Mac
2. Run podman run --rm -p 127.0.0.1:879:80 alpine echo 1

Describe the results you received

Error: preparing container 610b74d61baaee4bdf2b06c8d0e679dd059786c5ebc5eaf796338ba1872a984f for attach: something went wrong with the request: "listen tcp 127.0.0.1:879: bind: permission denied\n"

Describe the results you expected

Successfully binding to the specified port and echoing 1

podman info output

Client:        Podman Engine
Version:       5.7.1
API Version:   5.7.1
Go Version:    go1.25.5
Git Commit:    f845d14e941889ba4c071f35233d09b29d363c75
Built:         Wed Dec 10 15:58:02 2025
Build Origin:  pkginstaller
OS/Arch:       darwin/arm64

Server:       Podman Engine
Version:      5.7.1
API Version:  5.7.1
Go Version:   go1.25.4 X:nodwarf5
Git Commit:   f845d14e941889ba4c071f35233d09b29d363c75
Built:        Tue Dec  9 01:00:00 2025
OS/Arch:      linux/arm64

Podman in a container

No

Privileged Or Rootless

Privileged

Upstream Latest Release

Yes

Additional environment details

OS:

ProductName:		macOS
ProductVersion:		26.2
BuildVersion:		25C56

Hardware:

  Model Name: MacBook Pro
  Model Identifier: MacBookPro17,1
  Model Number: Z11B0000UD/A
  Chip: Apple M1
  Total Number of Cores: 8 (4 performance and 4 efficiency)
  Memory: 16 GB
  System Firmware Version: 13822.61.10
  OS Loader Version: 13822.61.10

Additional information

No response