Re: set -x path always returns 1 on fedora34 on arm64
Sorry, it is test -x instead of set -x. There are similar results for test - r file, [ -r file] and so on. On Wed, May 12, 2021, 13:34 Boleyn Su wrote: > Please refer to the subject. >
Re: set -x path always returns 1 on fedora34 on arm64
i dunno but, -x is for exe flag and -r for readable, and it never did not work On Wed, May 12, 2021, 10:32 Boleyn Su wrote: > Sorry, it is test -x instead of set -x. There are similar results for test > - r file, [ -r file] and so on. > > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: > > > Please refer to the subject. > > >
Re: set -x path always returns 1 on fedora34 on arm64
I know it is supposed to always work but it do break here. If anyone can reproduce it would be more convincing though. I am using the Fedora 34 container image from https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Container/aarch64/images/Fedora-Container-Base-34-1.2.aarch64.tar.xz On Wed, May 12, 2021, 16:37 Alex fxmbsw7 Ratchev wrote: > i dunno but, -x is for exe flag and -r for readable, and it never did not > work > > On Wed, May 12, 2021, 10:32 Boleyn Su wrote: > >> Sorry, it is test -x instead of set -x. There are similar results for test >> - r file, [ -r file] and so on. >> >> On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >> >> > Please refer to the subject. >> > >> >
Re: set -x path always returns 1 on fedora34 on arm64
i may can check it out later but dont count on it On Wed, May 12, 2021, 10:53 Boleyn Su wrote: > I know it is supposed to always work but it do break here. If anyone can > reproduce it would be more convincing though. I am using the Fedora 34 > container image from > https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Container/aarch64/images/Fedora-Container-Base-34-1.2.aarch64.tar.xz > > On Wed, May 12, 2021, 16:37 Alex fxmbsw7 Ratchev > wrote: > >> i dunno but, -x is for exe flag and -r for readable, and it never did not >> work >> >> On Wed, May 12, 2021, 10:32 Boleyn Su wrote: >> >>> Sorry, it is test -x instead of set -x. There are similar results for >>> test >>> - r file, [ -r file] and so on. >>> >>> On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >>> >>> > Please refer to the subject. >>> > >>> >>
Re: set -x path always returns 1 on fedora34 on arm64
On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: > Sorry, it is test -x instead of set -x. There are similar results for test > - r file, [ -r file] and so on. If "[ -r file]" is your code, then it fails because the "[" utility needs "]" as its last argument, and you are giving it "file]". Insert a space before that last "]". If that is not the code you are using, then consider posting the code you are using. If you don't, we can only really say "it works for me". > > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: > > > Please refer to the subject. > > -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: set -x path always returns 1 on fedora34 on arm64
I tested that it is the container image to blame by compiling the source code from both the host and the container and checking that it only breaks in the container. Maybe it is a libc bug or something. I will file a bug to Fedora later. Would be great if anyone can test the image. Note that the x86_64 image works as expected. On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < andreas.kah...@abc.se> wrote: > On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: > > Sorry, it is test -x instead of set -x. There are similar results for > test > > - r file, [ -r file] and so on. > > If "[ -r file]" is your code, then it fails because the "[" utility > needs "]" as its last argument, and you are giving it "file]". Insert a > space before that last "]". > That is just a typo. > If that is not the code you are using, then consider posting the code > you are using. If you don't, we can only really say "it works for me". > > > > > > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: > > > > > Please refer to the subject. > > > > > -- > Andreas (Kusalananda) Kähäri > SciLifeLab, NBIS, ICM > Uppsala University, Sweden > > . >
Re: set -x path always returns 1 on fedora34 on arm64
I just found someone facing the same issuse https://bugzilla.redhat.com/show_bug.cgi?id=1900021 On Wed, May 12, 2021, 17:25 Boleyn Su wrote: > I tested that it is the container image to blame by compiling the source > code from both the host and the container and checking that it only breaks > in the container. Maybe it is a libc bug or something. I will file a bug to > Fedora later. Would be great if anyone can test the image. Note that the > x86_64 image works as expected. > > > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < > andreas.kah...@abc.se> wrote: > >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: >> > Sorry, it is test -x instead of set -x. There are similar results for >> test >> > - r file, [ -r file] and so on. >> >> If "[ -r file]" is your code, then it fails because the "[" utility >> needs "]" as its last argument, and you are giving it "file]". Insert a >> space before that last "]". >> > That is just a typo. > >> If that is not the code you are using, then consider posting the code >> you are using. If you don't, we can only really say "it works for me". >> >> >> > >> > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >> > >> > > Please refer to the subject. >> > > >> >> -- >> Andreas (Kusalananda) Kähäri >> SciLifeLab, NBIS, ICM >> Uppsala University, Sweden >> >> . >> >
Re: set -x path always returns 1 on fedora34 on arm64
do you have instructions how to run the container i have an a64 phone i wanted to try with termux ( and debian inside ) but i dunno to spawn proot yet over the image, i think cause android fault chroot is not enuff.. but ill try soon On Wed, May 12, 2021, 11:58 Boleyn Su wrote: > I just found someone facing the same issuse > https://bugzilla.redhat.com/show_bug.cgi?id=1900021 > > On Wed, May 12, 2021, 17:25 Boleyn Su wrote: > > > I tested that it is the container image to blame by compiling the source > > code from both the host and the container and checking that it only > breaks > > in the container. Maybe it is a libc bug or something. I will file a bug > to > > Fedora later. Would be great if anyone can test the image. Note that the > > x86_64 image works as expected. > > > > > > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < > > andreas.kah...@abc.se> wrote: > > > >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: > >> > Sorry, it is test -x instead of set -x. There are similar results for > >> test > >> > - r file, [ -r file] and so on. > >> > >> If "[ -r file]" is your code, then it fails because the "[" utility > >> needs "]" as its last argument, and you are giving it "file]". Insert a > >> space before that last "]". > >> > > That is just a typo. > > > >> If that is not the code you are using, then consider posting the code > >> you are using. If you don't, we can only really say "it works for me". > >> > >> > >> > > >> > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: > >> > > >> > > Please refer to the subject. > >> > > > >> > >> -- > >> Andreas (Kusalananda) Kähäri > >> SciLifeLab, NBIS, ICM > >> Uppsala University, Sweden > >> > >> . > >> > > >
Re: set -x path always returns 1 on fedora34 on arm64
yea well i can only suggest using only newest versions, lower is nonsense On Wed, May 12, 2021, 13:15 Boleyn Su wrote: > I do not know how to run it on an Android phone either. BTW, I have fixed > my issue by updating dockerd to v20.10.6 following the suggestion in the > redhat bug tracker. > > Sent from https://boleyn.su/phone > > On Wed, May 12, 2021, 19:05 Alex fxmbsw7 Ratchev > wrote: > >> do you have instructions how to run the container >> i have an a64 phone i wanted to try with termux ( and debian inside ) but >> i dunno to spawn proot yet over the image, i think cause android fault >> chroot is not enuff.. but ill try soon >> >> On Wed, May 12, 2021, 11:58 Boleyn Su wrote: >> >>> I just found someone facing the same issuse >>> https://bugzilla.redhat.com/show_bug.cgi?id=1900021 >>> >>> On Wed, May 12, 2021, 17:25 Boleyn Su wrote: >>> >>> > I tested that it is the container image to blame by compiling the >>> source >>> > code from both the host and the container and checking that it only >>> breaks >>> > in the container. Maybe it is a libc bug or something. I will file a >>> bug to >>> > Fedora later. Would be great if anyone can test the image. Note that >>> the >>> > x86_64 image works as expected. >>> > >>> > >>> > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < >>> > andreas.kah...@abc.se> wrote: >>> > >>> >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: >>> >> > Sorry, it is test -x instead of set -x. There are similar results >>> for >>> >> test >>> >> > - r file, [ -r file] and so on. >>> >> >>> >> If "[ -r file]" is your code, then it fails because the "[" utility >>> >> needs "]" as its last argument, and you are giving it "file]". >>> Insert a >>> >> space before that last "]". >>> >> >>> > That is just a typo. >>> > >>> >> If that is not the code you are using, then consider posting the code >>> >> you are using. If you don't, we can only really say "it works for >>> me". >>> >> >>> >> >>> >> > >>> >> > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >>> >> > >>> >> > > Please refer to the subject. >>> >> > > >>> >> >>> >> -- >>> >> Andreas (Kusalananda) Kähäri >>> >> SciLifeLab, NBIS, ICM >>> >> Uppsala University, Sweden >>> >> >>> >> . >>> >> >>> > >>> >>
Re: set -x path always returns 1 on fedora34 on arm64
I do not know how to run it on an Android phone either. BTW, I have fixed my issue by updating dockerd to v20.10.6 following the suggestion in the redhat bug tracker. Sent from https://boleyn.su/phone On Wed, May 12, 2021, 19:05 Alex fxmbsw7 Ratchev wrote: > do you have instructions how to run the container > i have an a64 phone i wanted to try with termux ( and debian inside ) but > i dunno to spawn proot yet over the image, i think cause android fault > chroot is not enuff.. but ill try soon > > On Wed, May 12, 2021, 11:58 Boleyn Su wrote: > >> I just found someone facing the same issuse >> https://bugzilla.redhat.com/show_bug.cgi?id=1900021 >> >> On Wed, May 12, 2021, 17:25 Boleyn Su wrote: >> >> > I tested that it is the container image to blame by compiling the source >> > code from both the host and the container and checking that it only >> breaks >> > in the container. Maybe it is a libc bug or something. I will file a >> bug to >> > Fedora later. Would be great if anyone can test the image. Note that the >> > x86_64 image works as expected. >> > >> > >> > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < >> > andreas.kah...@abc.se> wrote: >> > >> >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: >> >> > Sorry, it is test -x instead of set -x. There are similar results for >> >> test >> >> > - r file, [ -r file] and so on. >> >> >> >> If "[ -r file]" is your code, then it fails because the "[" utility >> >> needs "]" as its last argument, and you are giving it "file]". Insert >> a >> >> space before that last "]". >> >> >> > That is just a typo. >> > >> >> If that is not the code you are using, then consider posting the code >> >> you are using. If you don't, we can only really say "it works for me". >> >> >> >> >> >> > >> >> > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >> >> > >> >> > > Please refer to the subject. >> >> > > >> >> >> >> -- >> >> Andreas (Kusalananda) Kähäri >> >> SciLifeLab, NBIS, ICM >> >> Uppsala University, Sweden >> >> >> >> . >> >> >> > >> >
Re: set -x path always returns 1 on fedora34 on arm64
Totally agree. The OS is a customized one shipping a very old dockerd and I am in no position to avoid using it. In fact, this is the very reason I am using a Fedora container on top of it. Sent from https://boleyn.su/phone On Wed, May 12, 2021, 19:19 Boleyn Su wrote: > For running it on an arm64 pc, you can run docker load or something > similar to load the image. The bug is not related to arm64 but the outdated > container runtime on the arm64 pc I am using. You can check the link to the > redhat bug tracker for more details. > > Sent from https://boleyn.su/phone > > On Wed, May 12, 2021, 19:05 Alex fxmbsw7 Ratchev > wrote: > >> do you have instructions how to run the container >> i have an a64 phone i wanted to try with termux ( and debian inside ) but >> i dunno to spawn proot yet over the image, i think cause android fault >> chroot is not enuff.. but ill try soon >> >> On Wed, May 12, 2021, 11:58 Boleyn Su wrote: >> >>> I just found someone facing the same issuse >>> https://bugzilla.redhat.com/show_bug.cgi?id=1900021 >>> >>> On Wed, May 12, 2021, 17:25 Boleyn Su wrote: >>> >>> > I tested that it is the container image to blame by compiling the >>> source >>> > code from both the host and the container and checking that it only >>> breaks >>> > in the container. Maybe it is a libc bug or something. I will file a >>> bug to >>> > Fedora later. Would be great if anyone can test the image. Note that >>> the >>> > x86_64 image works as expected. >>> > >>> > >>> > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < >>> > andreas.kah...@abc.se> wrote: >>> > >>> >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: >>> >> > Sorry, it is test -x instead of set -x. There are similar results >>> for >>> >> test >>> >> > - r file, [ -r file] and so on. >>> >> >>> >> If "[ -r file]" is your code, then it fails because the "[" utility >>> >> needs "]" as its last argument, and you are giving it "file]". >>> Insert a >>> >> space before that last "]". >>> >> >>> > That is just a typo. >>> > >>> >> If that is not the code you are using, then consider posting the code >>> >> you are using. If you don't, we can only really say "it works for >>> me". >>> >> >>> >> >>> >> > >>> >> > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >>> >> > >>> >> > > Please refer to the subject. >>> >> > > >>> >> >>> >> -- >>> >> Andreas (Kusalananda) Kähäri >>> >> SciLifeLab, NBIS, ICM >>> >> Uppsala University, Sweden >>> >> >>> >> . >>> >> >>> > >>> >>
Re: set -x path always returns 1 on fedora34 on arm64
good luck and wishes :) On Wed, May 12, 2021, 13:30 Boleyn Su wrote: > Totally agree. The OS is a customized one shipping a very old dockerd and > I am in no position to avoid using it. In fact, this is the very reason I > am using a Fedora container on top of it. > > Sent from https://boleyn.su/phone > > On Wed, May 12, 2021, 19:19 Boleyn Su wrote: > >> For running it on an arm64 pc, you can run docker load or something >> similar to load the image. The bug is not related to arm64 but the outdated >> container runtime on the arm64 pc I am using. You can check the link to the >> redhat bug tracker for more details. >> >> Sent from https://boleyn.su/phone >> >> On Wed, May 12, 2021, 19:05 Alex fxmbsw7 Ratchev >> wrote: >> >>> do you have instructions how to run the container >>> i have an a64 phone i wanted to try with termux ( and debian inside ) >>> but i dunno to spawn proot yet over the image, i think cause android fault >>> chroot is not enuff.. but ill try soon >>> >>> On Wed, May 12, 2021, 11:58 Boleyn Su wrote: >>> I just found someone facing the same issuse https://bugzilla.redhat.com/show_bug.cgi?id=1900021 On Wed, May 12, 2021, 17:25 Boleyn Su wrote: > I tested that it is the container image to blame by compiling the source > code from both the host and the container and checking that it only breaks > in the container. Maybe it is a libc bug or something. I will file a bug to > Fedora later. Would be great if anyone can test the image. Note that the > x86_64 image works as expected. > > > On Wed, May 12, 2021, 17:16 Andreas Kusalananda Kähäri < > andreas.kah...@abc.se> wrote: > >> On Wed, May 12, 2021 at 04:31:47PM +0800, Boleyn Su wrote: >> > Sorry, it is test -x instead of set -x. There are similar results for >> test >> > - r file, [ -r file] and so on. >> >> If "[ -r file]" is your code, then it fails because the "[" utility >> needs "]" as its last argument, and you are giving it "file]". Insert a >> space before that last "]". >> > That is just a typo. > >> If that is not the code you are using, then consider posting the code >> you are using. If you don't, we can only really say "it works for me". >> >> >> > >> > On Wed, May 12, 2021, 13:34 Boleyn Su wrote: >> > >> > > Please refer to the subject. >> > > >> >> -- >> Andreas (Kusalananda) Kähäri >> SciLifeLab, NBIS, ICM >> Uppsala University, Sweden >> >> . >> > >>>
Re: set -x path always returns 1 on fedora34 on arm64
On 5/12/21 1:34 AM, Boleyn Su wrote: Please refer to the subject. To wrap the discussion, this appears to be a docker-container-only problem and the result of a bug in glibc. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
