Bug 1721638

Summary:	Podman build segfaults on Dockerfiles with RUN instruction
Product:	Red Hat Enterprise Linux 8	Reporter:	Matthew Heon <mheon>
Component:	podman	Assignee:	Brent Baude <bbaude>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	dornelas, dwalsh, jligon, jnovy, jwboyer, lsm5, mheon, pthomas, santiago
Target Milestone:	beta	Flags:	pm-rhel: mirror+
Target Release:	8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	container-tools-rhel8-8010020190619122352.4985cc55	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 21:02:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Heon 2019-06-18 18:59:47 UTC

Description of problem:

The `podman build` command segfaults on building any Dockerfile containing a `RUN` instruction.

Version-Release number of selected component (if applicable):

Podman 1.4.1

How reproducible:

100%

Steps to Reproduce:
1. Create a dockerfile with the following contents

FROM fedora
RUN touch /tmp/test1

2. Run `podman build .` in the same directory as the Dockerfile

Actual results:

STEP 1: FROM fedora
STEP 2: RUN touch /tmp/test1
panic: runtime error: index out of range

goroutine 25 [running]:
<remaining error trace snipped>

Expected results:

STEP 1: FROM fedora
STEP 2: RUN touch /tmp/test1
STEP 3: COMMIT
--> 191f4f2be3bbb9a1398ad8a7f7de570d0480bf0ad19189f3a8c451dc1a368ba9

(Successfully built image)

Additional info:

Confirmed not a problem in Buildah - they landed a fresh release (1.9.0) in 8.1 with the fix.

Comment 8 errata-xmlrpc 2019-11-05 21:02:22 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3403