New pods are no longer deploying succesfully

[barnscott]

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

Description
Getting following error when starting a pod with "--pod new:name"

$ podman pod start -l
Error: error starting container e2081485c8c989c2668950dd74de53f63d03ca41f731cef7c252d7965ff6ea97: failed to expose ports via rootlessport: "listen tcp 0.0.0.0:9088: bind: address already in use\n"

Steps to reproduce issue, approach 1

podman create -d \
    --pod new:nextcloud \
    --name nc_app \
    -p 9088:80 \
    -v /path:/var/www/html \
    ...
    nextcloud

podman create -d \
    --pod nextcloud \
    --name nc_db \
    ...
    -v /path:/var/lib/postgresql/data \
    postgres

$ podman pod start -l
Error: error starting container e2081485c8c989c2668950dd74de53f63d03ca41f731cef7c252d7965ff6ea97: failed to expose ports via rootlessport: "listen tcp 0.0.0.0:9088: bind: address already in use\n"

Steps to reproduce issue, approach 2

podman pod create --name nextcloud

podman create -d \
    --pod nextcloud \
    --name nc_app \
    -p 9088:80 \
    -v /path:/var/www/html \
    ...
    nextcloud

podman create -d \
    --pod nextcloud \
    --name nc_db \
    ...
    -v /path:/var/lib/postgresql/data \
    postgres

$ podman pod start -l

In this second method, the pod and containers all deploy without error messages. However, the app is not accessabile at 9088, and the mapping is NOT reported via "podman port -a".

Describe the results you received:
The two methods I am familar with for deploying pods have stopped working(?)

Describe the results you expected:
Pod should deploy successfully. I am not expecting to see a port conflict.

Additional information you deem important (e.g. issue happens only occasionally):
Not sure when issue would have first started. I hadnt redeployed this container in weeks. I hadnt seen any issues during pod restarts.

Output of podman version:

$ podman version
Version:      2.0.4
API Version:  1
Go Version:   go1.14.6
Built:        Wed Dec 31 18:00:00 1969
OS/Arch:      linux/amd64

Output of podman info --debug:

$ podman info --debug
host:
  arch: amd64
  buildahVersion: 1.15.0
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.19-1.fc32.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.19, commit: 5dce9767526ed27f177a8fa3f281889ad509fea7'
  cpus: 8
  distribution:
    distribution: fedora
    version: "32"
  eventLogger: file
  hostname: barnix-org
  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.7.15-200.fc32.x86_64
  linkmode: dynamic
  memFree: 4083015680
  memTotal: 16739409920
  ociRuntime:
    name: crun
    package: crun-0.14.1-1.fc32.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.14.1
      commit: 598ea5e192ca12d4f6378217d3ab1415efeddefa
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  rootless: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.4-1.fc32.x86_64
    version: |-
      slirp4netns version 1.1.4
      commit: b66ffa8e262507e37fca689822d23430f3357fe8
      libslirp: 4.3.1
      SLIRP_CONFIG_VERSION_MAX: 2
  swapFree: 34359734272
  swapTotal: 34359734272
  uptime: 12h 45m 40.93s (Approximately 0.50 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /var/home/barn/.config/containers/storage.conf
  containerStore:
    number: 4
    paused: 0
    running: 4
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-1.1.2-1.fc32.x86_64
      Version: |-
        fusermount3 version: 3.9.1
        fuse-overlayfs: version 1.1.0
        FUSE library version 3.9.1
        using FUSE kernel interface version 7.31
  graphRoot: /var/home/barn/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 8
  runRoot: /tmp/1000
  volumePath: /var/home/barn/.local/share/containers/storage/volumes
version:
  APIVersion: 1
  Built: 0
  BuiltTime: Wed Dec 31 18:00:00 1969
  GitCommit: ""
  GoVersion: go1.14.6
  OsArch: linux/amd64
  Version: 2.0.4

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

$ rpm -q podman
podman-2.0.4-1.fc32.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes

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

[mheon]

Can you verify that nothing else on the host is using port 9088?

[Luap99]

Approach 1 doesn't work because there is a bug with the new: syntax. This will be fixed in the next release. #7152

Approach 2 doesn't work because you have to specify the port binding on the pod create command. The docs are not clear on this though. This should be improved with #7364. You might want to take a look if this is a good explanation to you.

If you still have the same error you should verify that there are no other processes already using this port as @mheon stated.

[barnscott]

@Luap99 you got it! approach 2 now works with that tweak.

ive been using approach 1 on this pod since january, so i was pretty confused; and i didnt find that bug report.

thanks!!