Binary for ARM64?
I am very interested in using wasp but the servers have Ubuntu ARM64 architecture and noticed you only provide a binary for x86. Any way I’d be able to this on my servers?
Or potentially set up a workflow so that I can run the binary locally but work on the codebase remotely?
7 Replies
Hi @bitmap. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Currently, Wasp provides prebuilt binary packages for Linux x86_64 and macOS x86_64 architectures. These binaries are installed via the Wasp installer script when users install Wasp on their machines source (https://github.com/wasp-lang/wasp/issues/1574).
For macOS machines with the new arm64 architecture, users can still use the macOS x86_64 binary via Rosetta, which emulates x86_64. However, there is currently no prebuilt binary package for Linux arm64 architecture source (https://github.com/wasp-lang/wasp/issues/1574).
The Wasp team is aware of the need for a binary package that works directly on arm64 and plans to add it once Github Actions (GA), which they use for building their binary packages, offers a GA runner that is macOS arm64. This is expected to be available in Q1 of 2024 source (https://github.com/wasp-lang/wasp/issues/1574).
In the meantime, if you need to run Wasp on a machine with an arm64 architecture, you can compile Wasp directly from the source for your machine. You can check the instructions on how to do that here (https://github.com/wasp-lang/wasp/tree/main/waspc).
As for setting up a workflow to run the binary locally but work on the codebase remotely, this would depend on the specifics of your setup and is not directly related to the Wasp binary itself. You might want to look into using a version control system like Git to manage your codebase across different machines.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @bitmap, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai Is there a tested solution to emulate and run the binary on Ubuntu ARM64
Let me check the knowledge base for you. One moment! :books:
----------------------
Currently, there is no tested solution provided by the Wasp team for emulating and running the Wasp binary on Ubuntu ARM64. The team primarily provides prebuilt binaries for Linux x86_64 and macOS x86_64 architectures source (https://github.com/wasp-lang/wasp/issues/1574).
However, you might be able to use a tool like QEMU, an open-source machine emulator and virtualizer, to emulate x86_64 on your ARM64 machine and run the Wasp binary. Please note that this is not a tested solution and might require additional setup and configuration.
For a more direct solution, you can compile Wasp directly from the source for your machine. You can check the instructions on how to do that here (https://github.com/wasp-lang/wasp/tree/main/waspc). This would require setting up the Haskell development environment on your machine.
The Wasp team is planning to add support for ARM64 once Github Actions, which they use for building their binary packages, offers a macOS ARM64 runner. This is expected to be available in Q1 of 2024 source (https://github.com/wasp-lang/wasp/issues/1574).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @bitmap, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Any updates on this from a contributor? Could I compile the binary myself?
Do you guys forsee any issues with doing this. Would like to save time where possible.
Hey @bitmap, this issue talks about the current limitations when working with ARM, so I recommend checking it out: https://github.com/wasp-lang/wasp/issues/2003
Imporatatnt point:
here are a couple of different things here though: one is building wasp CLI for ARM, and another is deploying an actualy Wasp app (server with its Dockerfile) to an ARM server. We might want to split this into multiple issues actually.And from what I got, you need the second thing (which I don't think is currently possible). But you also mention running the
wasp binary on the servers (the first thing), why would you need that? The normal flow is building everything locally and deploying regular JS projects to the servers.@Filip why wouldn't the second thing be possible?
deploying an actualy Wasp app (server with its Dockerfile) to an ARM server.Wasp apps are just Node.js + React + DB apps, so they should run fine on ARM64 irregardless if we have the CLI for ARM64?
Because our Dockerfile isn't compatible with ARM (not sure why though, check the issue and linked discussion for details)