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
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 fo
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
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 fi
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
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.
>
Please refer to the subject.
