Description of problem: bash builtin `test -x /` does return 1, rather then returning 0. This is only if running in a container on a ubuntu host. Version-Release number of selected component (if applicable): bash-5.0.17-2.fc33.x86_64 How reproducible: always Steps to Reproduce: 1. run a ubuntu host (e.g. 16.04 18.04 20.04) 2. podman run --rm -it registry.fedoraproject.org/fedora:rawhide /usr/bin/bash -c "test -x /" ; echo $? Actual results: returns 1 Expected results: returns 0 Additional info: / is executable, podman run --rm -it registry.fedoraproject.org/fedora:rawhide /usr/bin/test -x / works as expected, so does zsh. Also, podman and docker behave the same way. The issue appeared between 9 days ago [good] on this image: 45c2323870da: Pull complete Digest: sha256:e2a3cdb67c628da3d47f001ace122464b8c75f53940731288f5c006768c48a7c and 2 days ago [bad] Koshei list among others a glibc update since the last build [koshei] - but I am not sure whether the build [glibc] is the culprint. Note that this breaks CI testing on travis, as no native fedora VMs are available. [good] https://travis-ci.org/github/boutproject/BOUT-dev/jobs/742716679 [bad] https://travis-ci.org/github/boutproject/BOUT-dev/jobs/742975318 [koshei] https://koschei.fedoraproject.org/package/bash [glibc] https://koji.fedoraproject.org/koji/buildinfo?buildID=1640545 [upstream] https://github.com/boutproject/BOUT-dev/issue/2143
Correct original bug report link: https://github.com/boutproject/BOUT-dev/issues/2143
This is a known issue triggered by a recent update of glibc. See bug #1869030 comment #22 for details. *** This bug has been marked as a duplicate of bug 1869030 ***
*** This bug has been marked as a duplicate of bug 1900021 ***