Segfault when invoking "podman build" on a file

Solution Unverified - Updated -


  • running podman build on a file leads to segfault / core dump

    # podman build testbuild
      panic: runtime error: invalid memory address or nil pointer dereference
      [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x55f28c407eba]
      goroutine 1 [running]:
      panic(0x55f28cd69980, 0x55f28deec1a0)
      /usr/lib/golang/src/runtime/panic.go:722 +0x2c6 fp=0xc00065b340 sp=0xc00065b2b0 pc=0x55f28b28d106
      /usr/lib/golang/src/runtime/signal_unix.go:394 +0x3f0 fp=0xc00065b370 sp=0xc00065b340 pc=0x55f28b2a2e70
      main.checkIfFileExists(0xc0006286c0, 0x2a, 0x2)
      /builddir/build/BUILD/libpod-5cc92849f7fc9dd734ca2fd8f3ae8830b9a7eb26/_build/src/ +0x9a fp=0xc00065b3c0 sp=0xc00065b370 pc=0x55f28c407eba
       /usr/lib/golang/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc0004ab7e0 sp=0xc0004ab7d8 pc=0x55f28b2bbad1
       created by runtime.(*timersBucket).addtimerLocked
       /usr/lib/golang/src/runtime/time.go:169 +0x110
    Abort (core dumped)


  • Red Hat Enterprise Linux (RHEL) 8.2
  • podman-1.6.4-11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content