-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Bun + Open Runtimes integration issue #684
Comments
After adding the following into
The new error is:
|
Could you please verify if the CPU supports AVX2? You can do this by running |
I am facing same problem on both my local machine (Macbook), and Gitpod. Locally:
On Gitpod:
|
Can you try installing the baseline build? curl https://bun.sh/install | bash |
We've changed our Docker images since this issue was created. If you still run into this problem with the new images, please feel free to re-open this issue. |
Version
0.1.4 (using Docker jarredsumner/bun:edge)
Platform
Linux 58dc05b8fbc7 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022 x86_64 Linux
What steps will reproduce the bug?
feat-bun-runtime
: Feat: Bun runtime open-runtimes/open-runtimes#85cd runtimes/bun-edge
docker compose up -d
This spins up an HTTP server from
server.js
. The problem seems to be related toprocess.env
if I am not mistaken.How often does it reproduce? Is there a required condition?
Always, looks like.
What is the expected behavior?
Spin up an HTTP server with no error, and handle requests.
What do you see instead?
Either on start, on when a request is received, an crash occurs:
Additional information
Hey there 👋
I am a maintainer of Open Runtimes and we wanted to create a runtime that supports Bun, so our lovely community can start playing with this trendy JavaScript runtime 😎
Sadly, we hit some road bumps that seem to be related to Bun itself. We would love to hear back from you to get Bun working with Open Runtimes, allowing developers all around the world to run Bun as a serverless function for their projects.
The text was updated successfully, but these errors were encountered: