Hey everyone, I was wondering if anyone who has an...
# helpb
Benanna19
08/02/2021, 3:25 PMHey everyone, I was wondering if anyone who has an M1 mac is still having issues running supabase on docker? This is probably a docker issue but I was wondering if anyone had this issue and found a work around. Thanks team!
e
everconfusedguy
08/02/2021, 3:29 PMjust provision 8 GB of RAM to docker @User not kidding
everconfusedguy
08/02/2021, 3:29 PM😂
everconfusedguy
08/02/2021, 3:29 PMpostgrest container restarts in a loop if it doesnt have at least 4 GB of RAM.. the postgrest team is working on a native ARM build but till then the docker emulation for postgrest takes quite a bit of resources..not sure why
everconfusedguy
08/02/2021, 3:30 PMother than this issue, the latest docker compose works for me on a M1 mac
b
Benanna19
08/02/2021, 3:32 PMInteresting. I assume I was having the same issue with the postgrest container restarting in a loop. I was watching it go in and out of being 'connected' in Docker. I guess Ill wait for the team to build the native ARM. Thanks @User. I've been checking in from time to time on the issue haha.
Benanna19
08/08/2021, 7:14 PM@User, just curious, but if I have supabase running on another computer, older computer, do you think that would be why I get a docker error that says
Copy code
Error invoking remote method 'docker-start-container': Error: (HTTP code 304) container already started -Benanna19
08/08/2021, 7:14 PMIs is that just an error that I get when it goes into its loop
f
fergus
09/10/2021, 2:03 AMThis is what I see on my M1 installation. I'm not able to use the local docker instance. I get an exception and the app crashes. Works fine with the production database. I can access the local database fine from DataGrip but then I suppose that's because I'm accessing postgres directly from DataGrip while my application is making a rest call? The error is coming from the supabase-js library I think..
error accessing database: { message: 'name resolution failed' }