-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Issues when running quickstart on Apple silicon #2416
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
Comments
Update: retried quickstart on the latest version, and it seems that it's still unhappy with mysql, though the automatic switch to elasticsearch fixes the neo4j issue. Substituting mariadb for mysql still gives an error with the qemo emulator as before. Logs:
|
Same here. I followed this quickstart guide and got an error when I run the command: datahub docker quickstart Logs:
My environment:
|
@zkan I'm having this exact same issue while running |
I have the same issue. Is there any work around? |
@m-ketan No, not yet. |
in docker-compose file:
it will work for M1 |
I had the same error, both for for neo4j and mysql;
allowed me to start with neo4j via |
To resolve this issue for all users on m1 macs, can we commit the change of adding the platform attribute? Or will this impact non-m1 users? If it's fine, I'd happily create a PR - thanks! |
Hello @cmpadden Feel free to open a PR, I'll get someone with a non-m1 pc to validate. I'm on m1 myself too. |
@cmpadden : are you aware of the m1 specific quickstart file (without neo4j)? |
running |
Describe the bug
When running the quickstart on a MacOS machine with the M1 chip, there are a few problems:
arm64v8/mariadb
for mysql, andneo4j/neo4j-arm64-experimental:4.2.5-arm64
for neo4j).To Reproduce
Steps to reproduce the behavior:
./docker/quickstart.sh
.Expected behavior
Containers all start up correctly and are healthy.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: