-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
Laravel Octane with FrankenPHP fails with exit code 139 (only on ARM) #1031
Comments
I wonder if this is related to the |
@AlliBalliBaba We are using |
Oh I think you're right, I thought it was a binary, but it's actually just a shell script.. |
@AlliBalliBaba Thanks for the suggestion, I just added this in an PR and I'll test this later today. |
@AlliBalliBaba Just tested it and sadly this did not change anything. |
I noticed you have |
for me disable opcache its works. ARM too |
@putrafajarh You are right, I just deactivated Does anyone know why this happens and I how I can fix that? Normally @withinboredom Do you still want me to try disabling those other extensions? |
Could you report this to PHP directly? |
Thanks for the help, I just reported the issue in the PHP GitHub repo. |
What happened?
We are building an open-source Laravel application (solidtime) and our production Docker image is using FrankenPHP with Laravel Octane. The image is based on this open-source Docker image.
This works perfectly fine on x86_64. Recently, we added an ARM version of our image for self-hosting.
I tested this problem on a MacBook Pro with M1, but also on a Hetzner ARM server, and I got the same results.
When I start the application on an ARM system, the process exits with the status code 139. I could not find relevant information in the logs.
Since this is an open-source project, the images are publicly available on the Docker Hub.
If you need any additional information, I'm happy to provide them. If one of the maintainers is interested, I can also give temporary access to the Hetzner ARM server that I have been testing this issue on.
This might also be related to #566 since we are using the same Docker image as a basis. I still created a new issue since the original problem of the existing issue seams to be different from this one.
Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
aarch64
PHP configuration
Relevant log output
The text was updated successfully, but these errors were encountered: