-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
pidfd_open(2) system call is not supported #5803
Comments
As the error suggests, you'll want to see if you can upgrade your Linux Kernel. Since you're using WSL, you can run: |
running into the same error when I'm using debian 10 |
Same here with Debian 10. edit: Ended up having to change to a different image with Debian 12. |
Already tried it, but didn't work :( (The update itself don't work) |
Same error using the latest |
Not worked |
+1, any updates? |
linux/arm64 - https://gvisor.dev/docs/user_guide/compatibility/linux/arm64/#pidfd_open This means bun cannot be used as a runtime in GCP products including:
This also affects any 3rd party clouds that use GCP infrastructure (I believe Vercel is one, I imagine there's a few). Please remove this kernel call or provide an alternate path when it's not available. EDIT: some details to reproduce, the call is triggered somewhere inside the GCP authentication library. So you can use bun, until you try and authenticate to use any other GCP service (such as pubsub, firestore, cloud tasks, anything). They all use the same underlying auth library. If you were to try Google's PubSub sample inside cloud run using bun/docker it should fail. I'm sure there are other code paths that trigger this system call but this is the one we're hitting. |
This function was added in version 5.3 of the Linux kernel and doesn't appear to have been backported. Either bun needs to add a check/workaround for older versions, or you are forced to upgrade. |
I am encountering this while using |
Linux kernel must be >= 5.13, you are using 4.4 |
As explained here, users of GCP container-based environments have no control over the linux kernel version. This works fine when using node as a runtime. It's a bug in bun. |
To be clear, we will fix this so Bun works properly in GCP environments. |
I am also experiencing this error using official oven/bun:debian docker image. |
I encounter the same error when using puppeteer together with the latest oven/bun:slim image. |
I have implemented a workaround in #6724. When the next version of Bun is released please run |
What version of Bun is running?
1.0.2
What platform is your computer?
Linux 4.4.0-19041-Microsoft x86_64 unknown
What steps can reproduce the bug?
bun create next-app
What is the expected behavior?
The project is succefuly created
What do you see instead?
Aborting installation.
Additional information
Version WSL : 1.2.5.0
Version du noyau : 5.15.90.1
Version WSLg : 1.0.51
Version MSRDC : 1.2.3770
Version direct3D : 1.608.2-61064218
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Version de Windows : 10.0.19045.3448
The text was updated successfully, but these errors were encountered: