Inspection reports non published ports with "null"

[sshnaidm]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Regression in podman 3.4.0
When container image has EXPOSE ports and not all of them are published, it reports in inspection data this port with null. Before 3.4.0 it wasn't reported at all.

Steps to reproduce the issue:

1. Build image:

FROM alpine

EXPOSE 137 138 139

2. Run it with publishing only 2 ports:
   podman run -d --name test --publish 11138:138 --publish 11137:137 my_custom_image

3. Run inspect with podman 3.3.1 and 3.4.0

Describe the results you received:
With 3.3.1 as usual was before:

"Ports": {
                "137/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "11137"
                    }
                ],
                "138/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "11138"
                    }
                ]
            },

And with 3.4.0 it's different now:

"Ports": {
                "137/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "11137"
                    }
                ],
                "138/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "11138"
                    }
                ],
                "139/tcp": null
            },

Notice the "139/tcp": null now.
It came up with issue from ansible-podman collections - containers/ansible-podman-collections#320
Describe the results you expected:

I'd expect not to have "139/tcp": null in results. Is it intentional?

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:      3.4.0
API Version:  3.4.0
Go Version:   go1.16.8
Built:        Thu Sep 30 22:40:21 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.23.1
  cgroupControllers: []
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.30-2.fc34.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.30, commit: '
  cpus: 12
  distribution:
    distribution: fedora
    variant: workstation
    version: "34"
  eventLogger: journald
  hostname: sshnaidm.remote
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.14.9-200.fc34.x86_64
  linkmode: dynamic
  logDriver: k8s-file
  memFree: 795062272
  memTotal: 33377624064
  ociRuntime:
    name: crun
    package: crun-1.0-1.fc34.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.0
      commit: 139dc6971e2f1d931af520188763e984d6cdfbf8
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.12-2.fc34.x86_64
    version: |-
      slirp4netns version 1.1.12
      commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.0
  swapFree: 3473252352
  swapTotal: 8589930496
  uptime: 176h 43m 2.11s (Approximately 7.33 days)
plugins:
  log:
  - k8s-file
  - none
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries:
  192.168.2.52:5000:
    Blocked: false
    Insecure: true
    Location: 192.168.2.52:5000
    MirrorByDigestOnly: false
    Mirrors: null
    Prefix: 192.168.2.52:5000
  search:
  - docker.io
  - quay.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
store:
  configFile: /home/sshnaidm/.config/containers/storage.conf
  containerStore:
    number: 19
    paused: 0
    running: 14
    stopped: 5
  graphDriverName: overlay
  graphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-1.7.1-2.fc34.x86_64
      Version: |-
        fusermount3 version: 3.10.4
        fuse-overlayfs: version 1.7.1
        FUSE library version 3.10.4
        using FUSE kernel interface version 7.31
  graphRoot: /home/sshnaidm/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 350
  runRoot: /run/user/1000/containers
  volumePath: /home/sshnaidm/.local/share/containers/storage/volumes
version:
  APIVersion: 3.4.0
  Built: 1633030821
  BuiltTime: Thu Sep 30 22:40:21 2021
  GitCommit: ""
  GoVersion: go1.16.8
  OsArch: linux/amd64
  Version: 3.4.0

Package info (e.g. output of rpm -q podman or apt list podman):

podman-3.4.0-1.fc34.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Additional environment details (AWS, VirtualBox, physical, etc.):

[sshnaidm]

Probably it's from this commit: fefa0b3

[zhangguanzhang]

this behavior is same with docker

[Luap99]

As described in #11314 this is intentional to match the docker output.