Open korridor opened 3 days ago
I wonder if this is related to the mlocati/php-extension-installer
Docker only being available for linux/amd64
@korridor are you installing php extensions via RUN install-php-extensions ...
?
@AlliBalliBaba We are using install-php-extensions
in our docker image. mlocati/php-extension-installer
as far as I'm informed, is a shell script and I don't see any note in the repository saying that it only supports linux/amd64
. I think you are referring to the fact that the docker image is only available for linux/amd64
, but the official FrankenPHP image only copies the shell script from the docker image, so I think that should be irrelevant, but maybe I'm missing something.
Oh I think you're right, I thought it was a binary, but it's actually just a shell script..
Can you try installing gcc via apt-get install gcc
in your docker image? I noticed that gcc
seems to be outdated in the php arm
images for some reason, maybe updating it will fix the issue.
@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 pcntl
enabled, have you tried disabling/uninstalling the extension? Same with rdkafka
. I'm just wondering if maybe it is a bug with one of those extensions being run on a zts build.
for me disable opcache its works. ARM too
@putrafajarh You are right, I just deactivated opcache
and it works, thanks.
Does anyone know why this happens and I how I can fix that? Normally opcache
is pretty important for PHP performance, but to be honest, I'm not sure if this is still the case if you are using FrankenPHP.
@withinboredom Do you still want me to try disabling those other extensions?
Could you report this to PHP directly?
Do you still want me to try disabling those other extensions?
@korridor, no if you found the issue is in opcache, then it is as @dunglas said, this should be reported to PHP.
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