-
Notifications
You must be signed in to change notification settings - Fork 487
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
Segmentation fault during building on Mac M1 devices #159
Comments
The problem seems to be with one of those two lines:
|
Had the same issue, working when changing https to http:
|
The issue is described here https://docs.docker.com/docker-for-mac/release-notes/#known-issues
|
Seems like this is a Docker issue and we can't resolve this in Sail. |
For sure you could ;-) Use a newer Ubuntu Version will do the trick. |
@mludi I don't think we're ready yet to move to the newer Ubuntu. Forge still provisions Ubuntu 20.04 and we want to stick to the same version. |
@driesvints ok, I hadn't this information :-) Thx! |
Hey everyone, I just tried to replicate this on my M1 machine to see if we could find a different solution to this, but unfortunately I wasn't able to replicate this. Here's a log of the build for those interested into what a functional build would look like. Here's what I'm running:
Furthermore, in my Docker settings, I'm using the following settings:
Can you confirm that you're using the same Docker settings? Thanks! |
@claudiodekker I have this issue only on one of my M1 Macs, the other one works fine. I use the same settings you provided. |
@mludi Alright, and what do you see when running If you're running the (currently) latest version, the output should be If it's not that, I recommend running |
I retried everything with these versions:
Executing your command results in But no matter how, I get the Segmentation fault. |
Same here. |
Interesting.. I just updated my Docker to 20.10.7, build f0df350 (latest), and now I'm also getting a Segfault at the Node step. For everyone that's having this issue, I recommend to downgrade Docker to 20.10.6, build 370c289 or to stay on that version if you're already on it (for now), as it appears that the newer version is actively causing this problem. This older build works. Do note that downgrading Docker does mean you WILL lose your existing images/containers, as a 'Factory Reset' will be necessary. So be sure to make a backup / export of those images/containers first! |
That explains, why I could build the image in the past on the same machine. |
I can confirm that Downgrading helps. :) |
Huge thanks! :) |
Gonna re-open this until we've found a solution. We tried updating to 21.04 in the end but there were some PECL issues. I'll try to look into resolving those. |
I saw the latest release of Docker Desktop has separate M1 builds. Can anyone try that out to see if this issue is fixed with it? https://docs.docker.com/docker-for-mac/release-notes/#docker-desktop-351 |
@driesvints I am on the M1 latest build and the issue still exists. |
Hey all. I got a new PR up that should also fix the PECL issues. Can you all please try it to see if you're unblocked that way? #177 |
@driesvints that worked fine :-) Thx! But I got
|
@mludi ah thanks. You sure you rebuilded from scratch? |
@driesvints yes, I removed all docker images and gave a fresh rebuild. |
@TiiFuchs I had the same with
but
or
|
It will set some environment variables which are needed. Yes, this is the expected error until you change this |
@mludi Until I change what? I switched the laravel/sail package to the fix-m1-issues branch and the Dockerfile used contains all changes. Also this is not the initial Segmentation fault, it's a different error. |
@driesvints perfect, that's working now :-) |
I can confirm too, that it works now. |
That's not necessary, sail does that already. |
Cool, I'll mark it as ready for review. Thanks all. |
Still have the same issue. |
Description:
While building the laravel.test container with sail, it currently is not able to finish and resolves in an Segmentation fault during building...
Steps To Reproduce:
sail up -d
=> The build fails.
The text was updated successfully, but these errors were encountered: