-
Notifications
You must be signed in to change notification settings - Fork 184
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
uncaught target signal 11 (Segmentation fault) - core dumped, running a container on MacOS with M1 chip #253
Comments
Do we have any workaround for this. Still i am having the same issue. |
I've been trying to build the image by my own, but I failed 😅 I also tried building the image in a Linux machine targeting PD: I had that much troubles using M1 chip that I just changed the laptop to use Intel i7 again. Whole Development ecosystem not ready to use M1. |
Same problem here |
I guess until a bit more general issues around Docker, the portability of common images and the various tools are resolved for the M1 chips, you'd have to revert back to using the mock as a library or as a JUnit rule/extension... 🤷 |
Same here. Till the problem get fixed, you can build your own arm64-based docker image with a simple Dockerfile if this work-around works for you:
|
FYI I have deployed a mirror that supports arm64 to |
Finally received my M1 MacBook.
Afterwards, the S3Mock just starts up. |
I saw that too, but it never actually answered any requests for me:
|
Compare this to running our fork:
|
It works well now for me. Feel free to close this issue, if nothing else is left about it. Thanks for the fix!
|
just released version |
Error
Unable to start a container on new MacBook Pro with M1 chip
Reproduce
System
macOS Big Sur v11.1
Apple M1 chip
Relevant issue
Quoted from here
The text was updated successfully, but these errors were encountered: