Skip to content
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

[BUG] It's not possible to have a GitHub action build an arm64 docker image #1535

Closed
automaton82 opened this issue Jan 16, 2024 · 1 comment · Fixed by #1537
Closed

[BUG] It's not possible to have a GitHub action build an arm64 docker image #1535

automaton82 opened this issue Jan 16, 2024 · 1 comment · Fixed by #1537

Comments

@automaton82
Copy link
Contributor

Describe the bug
If you create a GitHub workflow action today that creates a docker image specifically for arm64, it will fail with a vague error:

#19 ERROR: process "/bin/sh -c yarn build" did not complete successfully: exit code: 1
------
 > [14/14] RUN yarn build:
1.967 yarn run v1.22.19
2.416 $ turbo run build
4.201 ld-linux-aarch64.so.1: /usr/src/packages/node_modules/turbo-linux-arm64/bin/go-turbo: Not a valid dynamic program
4.315 error Command failed with exit code 1.

To Reproduce
Clone this repo, then create a new GitHub workflow that contains the following in it:

     ... 
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v3

      - name: Setup Docker BuildX
        uses: docker/setup-buildx-action@v3
        
      - name: Build and push Docker image
        uses: docker/build-push-action@v5
        with:
          context: .
          file: ./Dockerfile
          push: true
          tags: flowise:latest
          platforms: linux/arm64

Expected behavior
This should build and be able to push without any errors.

Setup
This can be done fully on GitHub.

Additional context
This is due (or similar to) vercel/turbo#5650 and was fixed in a later version of turbo.

@automaton82
Copy link
Contributor Author

I opened a PR to fix this. It's an incredibly easy fix once the cause was found, simply allow turbo to update instead of being locked at that specific version. Unfortunately it was not easy to find the cause, and will definitely cause headaches for others.

The newer versions of turbo have it solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant