docker-node: [buildx/arm64] yarn and npm not able to download packages from internet

Meet the same issue on Github Actions Ci:

name: Build and Push Image to Docker hub

on:
  push:
    branches: ['main']
  workflow_dispatch:

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v2
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2
      - name: Login to Docker Hub
        uses: docker/login-action@v2
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      - name: Build and push
        uses: docker/build-push-action@v4
        with:
          context: .
          platforms: linux/amd64,linux/arm64
          push: true
          tags: usr/app:latest

Build and push linux/amd64 image cost about 2-3 mins, but build linux/arm64 cost about more than half an hour and always in the yarn install… state.

I think this is fairly reproducible. On my ubuntu machines, any Dockerfile that includes RUN npm .... will fail in this same way when either targeting an arm64 image, or running docker buildx build when the targets include an arm64 target.

I am not able to reproduce however on my macbooks.

Hi @LaurentGoderre ,

As I wrote, the same holds true for running in GitHub Action environments. I already had this idea, so I verified the issue by running the build on other platforms. Also, in every environment amd64 builds just fine.

What do you think I can further do, to help with this issue?

Thanks and best regards

Let me guess – you’re not building on an actual arm64 runner node which means the arm64 build is generated using QEMU. Emulation is slow, therefore there’s much higher risk of running into timeouts.

It may be still possible there’s an additional problem with the network connection which may be worth debugging (I do see ESOCKETTIMEDOUT in the logs) but I’m not sure if this is related to docker-node in any way.

While this seems plausible, I think it’s the common case that projects will build against an emulated environment. Would it not be an improvement to docker-node to perhaps update documentation in some way to call this out?

I had the same problem, but then I found this

docker run --privileged --rm tonistiigi/binfmt --install all

in the official documentation, which solved my problem. Further explanation will be found in the docs itself.

Config that worked for me to build the arm64 with yarn on GitHub actions:

Add this to your Dockerfile before RUN yarn install :

RUN yarn config set network-timeout 300000
RUN apk add g++ make py3-pip
RUN yarn global add node-gyp

RUN yarn install

1. Increase the network timeout set network-timeout 300000
2. Add additional dependencies
3. Install node-gyp

People on node 20 with npm 10 could try downgrading npm to v9 because v10 has a known bug where it opens an excessive amount of network connections, see https://github.com/npm/cli/issues/7072.

@mohsenasm I agree with you. Look’s like this effects node:20 (lts). I have downgraded my dockerfile to node:18-alpine3.19 and yarn install now works again.

Same here. Less than a minute locally vs. 8 minutes on average running in a Docker build step on GitHub Actions. I confirm we are building an arm64 image with Docker buildx official action.

Also, no way to get it working without using --network-timeout 100000.

It also stuck in #14 [dependencies 2/5] RUN yarn config set network-timeout 300000 for node:20-alpine and linux/arm/v7. Super weird!

I tried all approaches, even building on an arm64 machine without buildx or QEMU. However, I kept receiving a timeout error.

i’m stuck at yarn install too…

I had the same problem, but then I found this

docker run --privileged --rm tonistiigi/binfmt --install all

in the official documentation, which solved my problem. Further explanation will be found in the docs itself.

• tried without cache
• tried without qemu
• tried with the docker run command mentioned above
• using yarn install

not possible to run on github workflows

edit: Without anything else, this seems to fix it on our side https://github.com/JamesonRGrieve/Agent-LLM-Frontend/pull/14

@LiterallyWar This error can be reproduced with these docker files & GH workflows as well.

https://github.com/frappe/frappe_docker https://github.com/frappe/frappe_docker/actions/runs/4401435320/jobs/7707642818

@LiterallyWar I was just able to reproduce my Error:

 => [internal] load build context                                                                                                                                         0.0s
 => => transferring context: 779B                                                                                                                                         0.0s
 => [linux/amd64 2/7] WORKDIR /app                                                                                                                                        0.3s
 => [linux/amd64 3/7] COPY [package.json, package-lock.json, tsconfig.json, ./]                                                                                           0.0s
 => CANCELED [linux/amd64 4/7] RUN yarn                                                                                                                                   6.1s
 => [linux/arm64 2/7] WORKDIR /app                                                                                                                                        0.3s
 => [linux/arm64 3/7] COPY [package.json, package-lock.json, tsconfig.json, ./]                                                                                           0.0s
 => CANCELED [linux/arm64 4/7] RUN yarn                                                                                                                                   3.2s
 => [linux/arm/v7 2/7] WORKDIR /app                                                                                                                                       0.3s
 => [linux/arm/v7 3/7] COPY [package.json, package-lock.json, tsconfig.json, ./]                                                                                          0.0s
 => ERROR [linux/arm/v7 4/7] RUN yarn                                                                                                                                     0.1s
------
 > [linux/arm/v7 4/7] RUN yarn:
#0 0.128 exec /bin/sh: exec format error
------
Dockerfile:9
--------------------
   7 |     COPY ["package.json", "package-lock.json", "tsconfig.json", "./"]
   8 |
   9 | >>> RUN yarn
  10 |
  11 |     COPY ["./src", "./src"]
--------------------
ERROR: failed to solve: process "/bin/sh -c yarn" did not complete successfully: exit code: 1

After running docker run --privileged --rm tonistiigi/binfmt --install all it runs perfectly.

I’m using docker buildx for building the images and takes around 2 minutes including publishing the images. I don’t use docker/setup-qemu-action@v2 but I don’t use GitHub Actions.

Furthermore, I run it locally, and I’m using Colima as the daemon.

@PeterDaveHello I noticed you added the yarn label to this issue. I also checked this using npm with the exact same behavior as yarn.

Currently I am trying to run some network diagnostic inside the container. If I stumble upon something useful, I will let you know.

best regards