-
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 buildx hang on node:22-alpine (armv6/armv7) #2077
Comments
This is a known issue with the armv6 armv7. No solution has been found yet |
I believe the Alpine builds, except ppcle are working again |
Glade to hear will try it. |
armv6/7 still not working |
Yeah, I don't think the root cause of this has been found yet. |
I had the same issue with ARG BASE_IMAGE=node:20.14.0-alpine
FROM --platform=$BUILDPLATFORM ${BASE_IMAGE} AS builder
RUN /build/stuff
...
FROM --platform=$BUILDPLATFORM ${BASE_IMAGE}
COPY --from=builder /stuff ./
... |
@pabra I might be simpler to specify the platform in the command instead of in the Dockerfile like |
@pabra on github CI this will use the host arch, which does not solve my issue here. |
@LaurentGoderre @pheiduck I use this Dockerfile with this github action. And it now builds images for Not sure what you are doing, @pheiduck. I use docker buildx with qemu in CI, so |
Will try it |
|
I cannot believe this has gone on so long without a resolution since 18.x builds. Appears so many issues raised across multiple issues |
It seems the error is that it runs out of memory:
|
Unfortunately for us going back to older node isnt an option as the platform we use is now dependent on the newer node version, but of course this issue prevents us from being able to deploy—stuck between a rock and a hard place! Wish I had a way to help try and solve, thanks for everyone's time. |
A Workaround we found out is to copy ofter build result to the newer image |
Thanks so much for the suggestion, unfortunately I dont think that works for us as we cant run the build on an older version with the updated package we want to use (next.js v14). Fingers crossed this one gets solved 🤞 |
commented out arm v6/v7 builds due to on going issues nodejs/docker-node#2077
… working for arm/v7 ref: nodejs/docker-node#2077 Signed-off-by: Pranav C <pranavxc@gmail.com>
… working for arm/v7 ref: nodejs/docker-node#2077 Signed-off-by: Pranav C <pranavxc@gmail.com>
Environment
Expected Behavior
No hanging build on armv6/armv7
Current Behavior
build is hanging on
npm ci --omit=dev
Possible Solution
none
Steps to Reproduce
run docker deployment on github ci
Additional Information
Logs:
https://productionresultssa4.blob.core.windows.net/actions-results/c81c7c78-0f17-4d1b-bb6e-eedc5023c285/workflow-job-run-e07742bd-189a-5079-918b-43f8b2f94b89/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-05-04T18%3A34%3A48Z&sig=kywF%2F31fsM6a0PFRA%2BGMwEYu9RkOcGzkAq1EUZumrx8%3D&sp=r&spr=https&sr=b&st=2024-05-04T18%3A24%3A43Z&sv=2021-12-02
The text was updated successfully, but these errors were encountered: