podman: Pod creation fails due to missing bridge mode networking

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

/kind bug

Description

Using a current dev version from git master (2.0.0-dev) pods can no longer be created.

Steps to reproduce the issue:

We use podman in rootless mode, so we have created a dedicated technical user called fwd to operate podman.

  1. As user fwd create a pod with one port mapping:

    podman pod create -p 8080:8080 --name test
    ERRO[0000] PortMappings can only be used with Bridge mode networking 
    

Describe the results you received:

The pod creation immediately fails with ERRO[0000] PortMappings can only be used with Bridge mode networking using a current build from git master.

Describe the results you expected:

Pod creation succeeds. Actually the very same command worked prior to installing the latest build from git master. I have also tried using –network bridge but that didn’t help either.

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

  • podman is used/running in rootless mode
  • I run podman pased on a build from git master (using make package-install)

Output of podman version:

Version:            2.0.0-dev
RemoteAPI Version:  1
Go Version:         go1.12.12
Git Commit:         9c8f59905f675bcdfc753daffa0ff316c7d6c800-dirty
Built:              Fri Apr 17 06:35:26 2020
OS/Arch:            linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahversion: 1.14.8
  cgroupsversion: v1
  conmon:
    package: podman-2.0.0-1587101717.git0d2b5532.el8.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.7, commit: 9c8f59905f675bcdfc753daffa0ff316c7d6c800-dirty'
  cpus: 2
  distribution:
    distribution: '"centos"'
    version: "8"
  eventlogger: journald
  hostname: daisyt
  idmappings:
    gidmap:
    - containerid: 0
      hostid: 1020
      size: 1
    - containerid: 1
      hostid: 296608
      size: 65536
    uidmap:
    - containerid: 0
      hostid: 1020
      size: 1
    - containerid: 1
      hostid: 296608
      size: 65536
  kernel: 4.18.0-147.5.1.el8_1.x86_64
  memfree: 103735459840
  memtotal: 105331625984
  ociruntime:
    name: runc
    package: runc-1.0.0-15.2.el8.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: db2349efc4dc0001462089382d175ed38fdba742
      spec: 1.0.1-dev
  os: linux
  rootless: true
  runtimeinfo: {}
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-0.4.3-23.2.el8.x86_64
    version: |-
      slirp4netns version 0.4.3-beta.1
      commit: b04291ba84ca35ccc60bd009372a28f9ea7ef841
  swapfree: 1048571904
  swaptotal: 1048571904
  uptime: 15h 47m 57.99s (Approximately 0.62 days)
store:
  configfile: /home/fwd/.config/containers/storage.conf
  containerstore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphdrivername: overlay
  graphoptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.2-1.module_el8.1.0+272+3e64ee36.x86_64
      Version: |-
        fuse-overlayfs: version 0.7.2
        FUSE library version 3.2.1
        using FUSE kernel interface version 7.26
  graphroot: /home/fwd/.local/share/containers/storage
  graphstatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imagestore:
    number: 0
  runroot: /tmp/run-1020/containers
  volumepath: /home/fwd/.local/share/containers/storage/volumes
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
version:
  remoteapiversion: 1
  version: 2.0.0-dev
  goversion: go1.12.12
  gitcommit: 9c8f59905f675bcdfc753daffa0ff316c7d6c800-dirty
  built: 1587101726
  osarch: linux/amd64

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

podman-2.0.0-1587101717.git0d2b5532.el8.x86_64

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

We run podman on a bare metal CentOS 8 server.

cat /etc/os-release:

NAME="CentOS Linux"
VERSION="8 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="8"

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

Yes (though you can likely use SSH to localhost as a sudo-substitute). We really ought to document this better on our part, as well.