SIGSEGV nil pointer dereference

[zhiburt]

Issue Description

It is just a report of a panic.

Can't provide a lot of information.
Except that it's podman from ubuntu:22.04.

It maybe duplicate as well it can be fixed already.

	panic: runtime error: invalid memory address or nil pointer dereference
	[signal SIGSEGV: segmentation violation code=0x1 addr=0xa0 pc=0x55db773abd3d]
	
	goroutine 83 [running]:
	github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah.(*StageExecutor).Execute(0xc0003c56c0, 0x55db77eb7720, 0xc0002b4540, 0xc0001567d7, 0x40, 0xc00014cff7, 0x40, 0x0, 0x0, 0x0, ...)
		/usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah/stage_executor.go:1014 +0xf3d
	github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah.(*Executor).buildStage(0xc000429c00, 0x55db77eb7720, 0xc0002b4540, 0xc00041b9b0, 0xc000484140, 0x5, 0x8, 0x2, 0xc000293438, 0xc00041ab60, ...)
		/usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah/executor.go:480 +0x2cc
	github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah.(*Executor).Build.func3.1(0xc000429c00, 0xc0004a3a94, 0x55db77eb7720, 0xc0002b4540, 0xc000010178, 0xc000484140, 0x5, 0x8, 0x2, 0xc00074d2c0)
		/usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah/executor.go:659 +0x108
	created by github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah.(*Executor).Build.func3
		/usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/containers/buildah/imagebuildah/executor.go:656 +0xbe

[nalind]

The stable version appears to be podman 3.4.4, which used buildah 1.23.1. Is there any chance you could check if this is still happening with a more recent version?