-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
php (exit status 139; not expected) #1105
Comments
Could you show your Dockerfile please? Are you using the official FrankenPHP Docker image or downloading the static binary in Sail's container? If it's the later, you're likely encountering a known OpenSSL issue: https://frankenphp.dev/docs/known-issues/#buggy-php-extensions Switching to the official Docker image will fix it. |
I'm using Laravel sail, so I've never thought about Dockerfile.
And I got this file:
|
Hi, |
This could also be related to some environment access shenanigans we just fixed. Theoretically, that is the most probable cause of a segfault. |
This seems to be related to WSL2, I can reproduce but it works flawlessly on a native linux server. |
Are you using the static binary? If yes, switch to the Docker image or compiling manually FrankenPHP will likely fix the issue. |
We are using the solution provided with Sail / Octane on Laravel documentation. |
@MattLoyeD yes, it's unfortunate but the only way to prevent this crash is to fix php/php-src#13648. The PHP Foundation seems to be on it (php/php-src#14734), but in the meantime there is nothing we can do except recommending not using musl builds if using OpenSSL (which is used by default by Laravel). |
@dunglas I just want to ask silly question (probably), as the segmentation fault is there with frankenphp, and I see if we use the binary we have a problem with program will exit, but for strange reason, if I use octane laravel, with pcntl, it won't exit but it seems retry to rerun by itself. Is it by design or just a placebo effect, as I haven't seen any segmentation fault if I use the official octane with docker from frankenphp |
No, it's not a placebo effect. The Docker image works well because it uses FrankenPHP with glibc. The bug only affects the static binary because it is compiled with musl, not with glibc (glibc doesn't support static binaries). Using the Docker image or compiling from source instead of downloading the static binary (as Octane does by default) prevents the bug. |
Can you clarify if we can use the static-builder image to compile a binary? Or will that also break? For example, compile a static binary in the static builder Image, then copy it to a FROM scratch Image in multi stage builds. |
A static build uses musl's libc, which causes this bug. There's not really a way around it. |
Ah okay, thanks.. I thought it only happened if you use alpine for some reason. I saw some mentions of "don't use it on alpine" in the docs |
What happened?
Hello world! Please tell me how to solve the problem with frunkenphp. When conducting stress tests, an error constantly crashes:
At the moment, I have. Laravel 11, sail + octane. The error comes out after about 60 seconds of testing and 5 competitive queries.
docker-compose.yml:
Your help would be very helpful ❤️
Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
Relevant log output
The text was updated successfully, but these errors were encountered: