Bug 1910208 - Bash's executablity tests broken in a rawhide container
Summary: Bash's executablity tests broken in a rawhide container
Keywords:
Status: CLOSED DUPLICATE of bug 1900021
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Siteshwar Vashisht
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-23 06:13 UTC by Ville Skyttä
Modified: 2020-12-25 10:01 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-12-25 10:01:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ville Skyttä 2020-12-23 06:13:05 UTC
I'm trying to track down a problem in a rawhide based container that I'm doing upstream tests of bash-completion with. All executability checks done with bash builtins return with a non-zero value in it.

Reproducer:

$ docker pull vskytta/bash-completion:fedoradev
$ docker run --rm -it vskytta/bash-completion:fedoradev bash
# test -x /; echo $?
1
# [[ -x /bin/bash ]]; echo $?
1
# [ -x /usr/bin/env ]; echo $?
1

zsh is not affected, works fine. Ditto /usr/bin/test. Just the bash builtins seem to have the issue.

Dockerfile etc for the container:
https://github.com/scop/bash-completion/tree/docker-fedoradev

My docker host is Ubuntu 18.04.

The vanilla fedora:rawhide image is not affected. Something in my image provokes this, but I'm kind of out of good ideas where to start the hunt. One idea would be to bisect the image build by slimming the installed package set gradually but that's a slow process, I'd hope there's a quicker/more straightforward way that could be tried first.

Comment 1 Kamil Dudka 2020-12-25 10:01:45 UTC

*** This bug has been marked as a duplicate of bug 1900021 ***


Note You need to log in before you can comment on or make changes to this bug.