Hide Forgot
Description of problem: When launching the `oc start-build foo --from-dir=. --wait --follow` command and a file with an accented character in the name like 'é' is present in the directory, the build fails with the error "error: unable to extract binary build input, must be a zip, tar, or gzipped tar, or specified as a file: exit status 1". Version-Release number of selected component (if applicable): How reproducible: ❯ oc start-build foo --from-dir=. --wait --follow Uploading directory "." as binary input for the build ... . Uploading finished build.build.openshift.io/foo-57 started Adding cluster TLS certificate authority to trust store Receiving source from STDIN as archive ... Adding cluster TLS certificate authority to trust store Adding cluster TLS certificate authority to trust store Caching blobs under "/var/cache/blobs". error: build error: no FROM image in Dockerfile error: the build test-build/foo-57 status is "Failed" ❯ touch é ❯ oc start-build foo --from-dir=. --wait --follow Uploading directory "." as binary input for the build ... . Uploading finished build.build.openshift.io/foo-58 started Adding cluster TLS certificate authority to trust store Receiving source from STDIN as archive ... error: unable to extract binary build input, must be a zip, tar, or gzipped tar, or specified as a file: exit status 1 error: the build test-build/foo-58 status is "Failed" Steps to Reproduce: 1. oc start-build foo --from-dir=. --wait --follow 2. touch é 3. oc start-build foo --from-dir=. --wait --follow Actual results: error: unable to extract binary build input, must be a zip, tar, or gzipped tar, or specified as a file: exit status 1 error: the build test-build/foo-58 status is "Failed" Expected results: Build Should not fail if there are such files/dir Additional info: Similar as https://bugzilla.redhat.com/show_bug.cgi?id=1673806
What version(s) of the oc client are being used? Please provide the output of `oc version`.
Different versions. I have been able to trigger it with 4.6.16 oc client.
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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-2021:2438