once https://bugzilla.redhat.com/show_bug.cgi?id=1810069 is resolved, devex team needs to use this bug to update the deps to pick up the buildah fix.
I don't know that you can get the buildah version (since we're just vendoring buildah code in). So we'd just have to confirm that the commit that image was built from, included the vendored changes we expect. But i don't think this was actually a verification failure. Look at your output: STEP 3: ADD ./f${foo} /tmp/foo error: build error: error building at STEP "ADD ./f${foo} /tmp/foo": no files found matching "/tmp/build/inputs/foo": no such file or directory It resolved the path correctly using the env var substitution ("/tmp/build/inputs/foo"). The reason it failed is you didn't actually provide a "foo" file in your build inputs, not because the path wasn't resolved correctly. Do this in the directory where you have your dockerfile: $ touch foo $ oc start-build --from-dir .
@Ben Now verified in version:4.5.0-0.nightly-2020-03-30-203132, linked case:OCP-28937 and Add test for origin, could you help to review the pr:https://github.com/openshift/origin/pull/24800, thanks.
Dropping dependency on the buildah bug fix, as it has already landed.
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:2409