-
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 error with Docker on Apple silicon/Arm64 #162
Comments
Thanks @SamuelMwangiW helped me :) |
@DougThwaites awesome!! Hope as support for Docker on arm64 improves, these kinks get worked out. Glad to have helped |
Hey @SamuelMwangiW. Would appreciate a PR to the docs if you're willing. Thanks! |
Will gladly do so. Thanks |
Thanks 😊 |
Thanks @SamuelMwangiW, only a note: If you already have a project just do this: cd YOU_PROJECT
curl https://laravel.build/laravel | sh
cd laravel
./vendor/bin/sail up -d --build
./vendor/bin/sail down
cd ..
rm -rf vendor
cp -r laravel/vendor vendor
./vendor/bin/sail up --build The same commands, only copy the vendor folder at your project. 🚀 |
@supermavster this has since been fixed in #169 and haven't experienced it in a long time. Thanks for your offer to assist, much appreciated |
Ah okey sorry I don't know about that, thanks again :D |
Description:
I am documenting a notorious error specific to docker on Arm that results to
apt-key
failing with the error below:The failure occurs at the following line in the
Dockerfile
:curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
My Solution
Publish the sail assets by running
php artisan sail:publish
and delete the following lines the publishedDockerfile
:As a consequence, you will loose access to running
yarn
via the sail container but as an alternative you can always accessnpm
that comes bundled withnodejs
and you can verify this by runningsail npm --v
I understand that the issue is not specific to Laravel Sail and will close it immediately but are posting it here hoping to assist a future user who may discover it via an issue search or good old Google
Steps To Reproduce:
On an M1 iMac, run the following:
The text was updated successfully, but these errors were encountered: