On Tue, 2026-01-20 at 10:41 +0100, naji green wrote: > Hello, > > I'm reporting this tar error. > > Summary: > > a Dockerfile arm build (QEMU) fail on this command: > > RUN tar xzf /tmp/Python-3.10.9.tgz -C /tmp > > Issue: > > [36m#21 [stage-1 10/29] RUN tar xzf /tmp/Python-3.10.9.tgz -C /tmp[0m > [36m#21 0.269 tar: Python-3.10.9/Mac: Cannot mkdir: Invalid > argument[0m > [36m#21 0.269 tar: Python-3.10.9/Mac/README.rst: Cannot open: Invalid > argument[0m > [36m#21 0.269 tar: Python-3.10.9/Mac/Icons: Cannot mkdir: Invalid > argument[0m > [36m#21 0.269 tar: Python-3.10.9/Mac/Icons/PythonLauncher.icns: > Cannot open: Invalid argument[0m > [36m#21 0.270 tar: Python-3.10.9/Mac/Icons/IDLE.icns: Cannot open: > Invalid argument[0m > [36m#21 0.271 tar: Python-3.10.9/Mac/Icons/PythonCompiled.icns: > Cannot open: Invalid argument[0m > [36m#21 0.271 tar: Python-3.10.9/Mac/Icons/ReadMe.txt: Cannot open: > Invalid argument[0m > [36m#21 0.272 tar: Python-3.10.9/Mac/Icons/PythonSource.icns: Cannot > open: Invalid argument[0m
This does look a bit like the kind of output we were seeing in the Yocto Project when running builds on hosts with newer versions of tar as patched by Redhat. Over time it appeared in our Rocky 9 / Alma 9 Centos Stream9 hosts as the fix was applied. It was triggered by this backport from tar upstream: https://cgit.git.savannah.gnu.org/cgit/tar.git/commit/?id=75b03fdff48916bd0654677ed21379bdb0db016d which uses the openat2 syscall/glibc function which is only available in newer glibcs. Our pseudo fakeroot emulation library didn't support openat2 and this caused failures like the above in tar. Our bugzilla entries tracking the issue were: https://bugzilla.yoctoproject.org/show_bug.cgi?id=16117 https://bugzilla.yoctoproject.org/show_bug.cgi?id=16126 I suspect something to do with the openat2 syscall in your docker environment might be causing it. Cheers, Richard
