-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker build with GitHub Actions failed on multi arch with node:alpine #1798
Comments
This also looks to be affecting another project: https://github.com/benphelps/homepage/actions/runs/3382149679 Going from -FROM node:current-alpine
+FROM docker.io/node:18-alpine fixes it. Hard for me to tell if this is a problem with the image or Node at this point. |
I've stumbled upon the same issue in n-thumann/IPTV-ReStream#188. This may be an issue related to / in qemu, because running the same command on a natively on Alpine @ armv7 (Raspberry Pi in this case) doesn't cause any issues:
I also tried to strace and noticed that |
This is the same issue as #1794. On Node 18 everything is OK, on Node 19 ( |
Node 19+ on Alpine seems to be broken on ARMv7: nodejs/docker-node#1798 Signed-off-by: David Mehren <git@herrmehren.de>
…`npm i` (`npm ci`) hangs forever from node `19`. Related issue: nodejs/docker-node#1798
Still reproduces on Node v20 images. |
I did some investigation and it looks like this is caused by qemu, which is used internally in Docker to emulate foreign architectures, e.g. when running a ARMv7 binary on a x86_64 host.
|
This seems to be indeed caused by a bug in qemu and is tracked in https://gitlab.com/qemu-project/qemu/-/issues/1729. |
It is known issue that `npm install` is stuck when building on platforms arm/v6 and arm/v7 of Docker images Node v19 and Node v20. See nodejs/docker-node#1829 and nodejs/docker-node#1798
It seems that this is resolved with QEMU 8.1.0. There are still many |
With tonistiigi/binfmt#144 (QEMU 8.1.4) and |
…s are failing with qemu multiarch builds nodejs/docker-node#1798
I've tracked the issue some time now. Is it correct, that the root cause can be pinned down to the qemu bug? There does not appear to be anyone taking up the matter. |
qemu-project/qemu#1729 has been closed recently, but the problem still occurs using latest image of |
Environment
Expected Behavior
The build is expected to complete without error, see: https://github.com/manuc66/node-hp-scan-to/actions/runs/3278864778/jobs/5397750728
Current Behavior
The build fail due to a timeout, see : https://github.com/manuc66/node-hp-scan-to/actions/runs/3304345713/jobs/5453599065
Possible Solution
I switched back to node:18-alpine and the build is working again, see: https://github.com/manuc66/node-hp-scan-to/actions/runs/3356995905/jobs/5562501857
The text was updated successfully, but these errors were encountered: