podman build requires runc

[quarckster]

Is this a BUG REPORT or FEATURE REQUEST?

/kind bug

Description

podman build requires runc to be presented in the PATH and it doesn't respect containers.conf.

Steps to reproduce the issue:

1. Uninstall runc
2. Install crun
3. Create $HOME/.config/containers/containers.conf with the following content:

   [engine]
   runtime="crun"

4. Start building a container image with podman build command

Describe the results you received:
Building fails with the error:

exec: "runc": executable file not found in $PATH

Describe the results you expected:

podman build should respect containers.conf and use the engine from it.

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

Specifying runtime explicitly podman --runtime=crun build makes it working.

Output of podman version:

Version:      3.0.0
API Version:  3.0.0
Go Version:   go1.15.2
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.19.2
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.26, commit: '
  cpus: 8
  distribution:
    distribution: neon
    version: "20.04"
  eventLogger: journald
  hostname: thinkpad-t480s
  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.4.0-65-generic
  linkmode: dynamic
  memFree: 1222160384
  memTotal: 16664195072
  ociRuntime:
    name: crun
    package: 'crun: /usr/bin/crun'
    path: /usr/bin/crun
    version: |-
      crun version 0.17.6-58ef-dirty
      commit: fd582c529489c0738e7039cbc036781d1d039014
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +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
    selinuxEnabled: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 1.1.8
      commit: unknown
      libslirp: 4.3.1-git
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.4.3
  swapFree: 893382656
  swapTotal: 1023406080
  uptime: 12h 41m 16.79s (Approximately 0.50 days)
registries: {}
store:
  configFile: /home/dmisharo/.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: /usr/bin/fuse-overlayfs'
      Version: |-
        fusermount3 version: 3.9.0
        fuse-overlayfs: version 1.4
        FUSE library version 3.9.0
        using FUSE kernel interface version 7.31
  graphRoot: /home/dmisharo/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 103
  runRoot: /run/user/1000/containers
  volumePath: /home/dmisharo/.local/share/containers/storage/volumes
version:
  APIVersion: 3.0.0
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.15.2
  OsArch: linux/amd64
  Version: 3.0.0

Package info:

apt list podman
Listing... Done
podman/unknown,now 100:3.0.0-1 amd64 [residual-config]
podman/unknown 100:3.0.0-1 arm64
podman/unknown 100:3.0.0-1 armhf
podman/unknown 100:3.0.0-1 s390x

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.):
I found the issues on my physical machine.

[mheon]

@rhatdan I thought we fixed this one? Do we need a newer Buildah than 1.19.2?

[Luap99]

I think this is a dup of #9365

[mheon]

Concur. I'll close it as a dupe.