-
Notifications
You must be signed in to change notification settings - Fork 363
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
Terrarium image platform prevents running on OSX M1 #800
Comments
What tool are you using to run containers on your machine? Docker Desktop includes a virtualization layer that translates the x86 instructions to ARM, so while it's not ideal, everything should still work despite the warning. I'm also currently running on an M1 Mac and it's working for me. |
Hi @malexw. Suspecting that the actual initial make command did complete successfully I attempted to run both
Considering that the message is suggesting that it could not find the correct image to pull, and not that docker could not run the image I added an explicit instruction to the docker compose file to pull the arm64 image expecting that then the Docker Desktop virtualisation layer would handle it.
This seemed to worked as expected as I know see this:
I will keep investigating my end why docker would not consider the amd64 image as a suitable image to pull if the arm64 image does not exist and why I had to be explicit in the Docker compose file. Yet this maybe a helpful workaround if anyone else is experiencing the same problem. If you have any input that may assist in why this may occur it would be very well recieved. Thanks again. |
Thanks @unfixa1. I will take a look. |
What is the issue?
After installing pipx and poetry and seeting up the tavily account the command
make first-run
seemed to be running well.Yet after downloading all of the docker images required and building those necessary the process got stuck attempting to complete the stack startup due to Terrarium's image not matching the host.
Is there a workaround for this?
Additional information
No response
The text was updated successfully, but these errors were encountered: