Skip to content
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

Local development - WARN exited: octane_00 (exit status 139; not expected) #79

Open
iamvincentong opened this issue May 19, 2024 · 6 comments
Labels
invalid This doesn't seem right

Comments

@iamvincentong
Copy link

iamvincentong commented May 19, 2024

I performed the following steps to set up my Laravel project with Docker:

  1. Created a new Laravel project.
  2. Navigated to the newly created Laravel project directory and installed Laravel Octane.
  3. After installing Octane, cloned directory contents, including the deployment directory, Dockerfile, and .dockerignore, into the Laravel project directory.
  4. In the Laravel project directory, ran the following commands:

docker build -t octane-test1:latest -f FrankenPHP.Dockerfile .

docker run -p 80:8000 --rm octane-test1:latest

I encountered the following errors (as shown in the screenshot below):
SCR-20240519-pngd

Could someone assist with troubleshooting this issue? Thank you.

@iamvincentong iamvincentong changed the title WARN exited: octane_00 (exit status 139; not expected) Local development - WARN exited: octane_00 (exit status 139; not expected) May 19, 2024
@denistorresan
Copy link
Contributor

Hi @iamvincentong are you running it on Mac arm64 / v8 or similar ?

@iamvincentong
Copy link
Author

Yes running on Mac M3 Max arm64.

@denistorresan
Copy link
Contributor

I'm running the same problem on a Mac arm64 of my customer with a tested application that run perfectly on Windows and Linux.
Actually I'm unable to test it because I don't have a mac to test it, but seems there's an incompatibility based on arm platform (?!)

@jbl-scf
Copy link

jbl-scf commented May 24, 2024

@iamvincentong have you try with jit disabled?

@denistorresan
Copy link
Contributor

hi @iamvincentong finally I got the chance to try on a Mac M2 and disabling JIT it works.
I changed on deployments/php.ini:

opcache.jit = disable

@smortexa
Copy link
Member

smortexa commented Jun 7, 2024

First, these Dockerfiles are intended for production, not development. Second, this is an upstream issue. You can follow it in dunglas/frankenphp.

@smortexa smortexa added the invalid This doesn't seem right label Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

4 participants