Bug 1817175
| Summary: | [4.4.z] buildah is not expanding env vars in file paths | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Adam Kaplan <adam.kaplan> |
| Component: | Build | Assignee: | Tom Sweeney <tsweeney> |
| Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, bparees, dwalsh, jcantril, jnovy, jokerman, nalin, tsweeney, wewang, wjiang, wzheng |
| Target Milestone: | --- | Flags: | adam.kaplan:
needinfo-
|
| Target Release: | 4.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | buildah-1.11.6-6.rhaos4.4.el8 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: A code change inadvertently removed variables set by the 'ENV' statement in a Dockerfile from the internal list of variables to use when later resolving variable arguments in the Dockerfile.
Consequence: Variables defined in a Dockerfile like 'ENV VERSION=0.0.1' would not later resolve in statements like 'COPY file-${VERSION}.txt /'. In this second statement, the '${VERSION}' variable resolved to a blank string ("") rather than "0.0.1" as it should have.
Fix: The code was updated to also add variables defined by the ENV statement into the internal list of variables.
Result: 'ENV' statements now resolve as intended.
|
Story Points: | --- |
| Clone Of: | 1810174 | Environment: | |
| Last Closed: | 2020-05-18 13:35:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1810174 | ||
| Bug Blocks: | 1810069, 1822207 | ||
|
Comment 15
Tom Sweeney
2020-05-12 13:11:23 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/RHBA-2020:2133 |