Thanks Marcin. I tested your solution but by me it still gets stuck at
the same point. Here's what I did:
$ tune2fs -O ^dir_index /dev/sda1
$ tune2fs -l /dev/sda1
tune2fs 1.44.2 (14-May-2018)
Filesystem volume name:
Last mounted on: /
Filesystem UUID: c8fee0cb-a610-4fa5-aab8-c
and tweaks sysctl
./qemu.sh # register qemu so you are able to run containers from other
architectures
./build.sh # try to build the docker image. Process should get stuck
in a 100% CPU loop after a while
Originally reported by, and test case developed by,
Philippe Vaucher.
To manage
I tried several workarounds including removing `dir_index` from ext4
partitions and using a 32 bit qemu-user-static version, but it does not
work:
The process still gets stuck in a loop involving `getdents64`:
```
root@earth:~# file /usr/bin/qemu-arm-static
/usr/bin/qemu-arm-static: ELF 32-bit L
** Summary changed:
- qemu-arm-static 100% CPU when cross-compiling emacs on alpine
+ qemu-arm-static stuck with 100% CPU when cross-compiling emacs
** Description changed:
Hello,
I'm trying to build multi-arch docker images for
https://hub.docker.com/r/silex/emacs.
Here is the mac
Public bug reported:
Hello,
I'm trying to build multi-arch docker images for
https://hub.docker.com/r/silex/emacs.
Here is the machine I'm building on (hetzner cloud machine):
root@ubuntu-4gb-fsn1-1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18
Thanks. It matches my bug because ubuntu:18.04 has a glibc 2.27 while
alpine 3.9 has glib 2.58, and your bug report mentions that 2.27 has not
the bug, so it makes sense.
However I don't see how not having the host filesystem as ext4 would
change anything, can you elaborate? Also, what filesystem
Okay, currently testing XFS. Using newer version of glibc on alpine
triggered other problems, like 0% CPU processes stuck on FUTEX_WAIT.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1861161
Title:
Building on XFS does the same thing :-( To test I bind mounted my XFS
partition on `/var/lib/docker` so everything docker was stored on XFS.
Not sure if this is what you meant.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Is there a workaround for this? I tried:
- Building on an XFS partition.
- Building from ubuntu:16.04 so the host has glib <2.27.
It looks like the only way is to have the chroot with glib <2.27, and in
alpine images glib is at minimum 2.56.
If the bug is fixed in glib maybe I can install glib f
Sorry, meant `< 2.28` above.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1805913
Title:
readdir() returns NULL (errno=EOVERFLOW) for 32-bit user-static qemu
on 64-bit host
Status in QEMU:
Ne
Ah, great thanks. It looks like there are patches that fix qemu,
although the setup looks a bit complex. I'll report if I get something
going.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1805913
Ti
11 matches
Mail list logo