https://supabase.com/ logo
Join DiscordCommunities
Powered by
Okay, new set of errors that I'm getting. When I d...
# help
a
Okay, new set of errors that I'm getting. When I do 
docker compose up
, I get 
supabase-storage   | exec /bin/sh: exec format error
and 
supabase-meta      | exec /bin/postgres-meta: exec format error
on run. This causes everything else to fail because it can't connect to the database. What can I do to resolve this?
n
Okay, new set of errors that I'm getting. When I do 
docker compose up
, I get 
supabase-storage   | exec /bin/sh: exec format error
and 
supabase-meta      | exec /bin/postgres-meta: exec format error
on run. This causes everything else to fail because it can't connect to the database. What can I do to resolve this?
Hello @Aav! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates. Want to change the title? Use the ``/title`` command! We have solved your problem? Click the button below to archive it.
j
It sounds to me like the networking part of the docker-compose file might not be getting checked because of the change in docker-compose version number.
n
Aav (2022-05-11)
a
I wound up reinstalling docker from source (rather than 
apt
) and reset the repo from source.
n
exec format error on run
j
Good call
a
Sadly, that didn't fix it.
Guess I'll go for one more nuke and reinstall
so that didn't do it
j
What version was specified in the docker-compose file?
I feel like the issue is docker-compose not docker. What version is it running?
a
3.8 is the version specified in 
docker-compose.yml
that's the latest docker compose from the docker repo
j
What version was originally specified in the docker-compose.yml?
a
3.8 per the github.
And this is fresh fresh, I just did a new 
git clone
after doing 
rm -rf
on my previous attempt.
j
Noice
a
So unless there's something wrong with my system I honestly can't figure it out.
although I also can't locate 
docker-entrypoint.sh
which I feel like would be helpful for troubleshooting this whole mess
j
If you do me the favour to link to the docker-compose.yml file I'll quickly take a look
a
yeah sure
j
Are you running it with some sort of env file?
a
yeah, I did 
cp .env.example .env
j
Which containers come up and which fail?
a
Studio and Kong come up, rest comes up and then fails to connect to the DB, db, storage, and meta crash with exec format error
j
Oh so DB is crashing with the exec format error?
a
yeah
j
What architecture is the device you're running on? 86, 64, arm?
a
ARM
j
There's your issue 😦
a
it's an oracle cloud Ampere compute platform
wait for real
noooo
j
Yeap
a
bleeeeeehhhhhhhhhhh
j
You in Australia?
a
nah
US
Why?
j
Just curious if there were any restrictions on where you could host
Google has a free tier: https://cloud.google.com/free
a
ah yeah nope not afaik
I'm running with Oracle rn because their free tier is freaking fantastic
j
Well then if you want to contrib to supabase, you could potentially look at their dockerfiles and help create some which use the arm versions of what they rely on?
Surely there's an arm postgres for example
a
there is yeah
I'm using it rn
j
Noice
a
I can't find the dockerfiles anywhere
otherwise I'd modify them
j
a
yeah I'm looking at them now
have you seen the actual dockerfile lurking around anywhere though?
if so I could just patch that and hope it works (if it does I'd PR it obv)
oh it looks like it's only the postgres image that needs arm64 support
j
@Aav you could skip that step by just adding 
network: host
to the docker compose file and then connect it to your existing arm64 postgres db to see if you can get it up and running...
a
oh that's a possibility that I hadn't thought of, thanks
let's see if that works
ugh
I've been hunting for where to put 
network: host
and can't find it
Hm it also looks like I might just be able to downgrade the postgres version to 14.1.0.15 instead of 14.1.0.21 EDIT: That did not fix it. I guess I shall wait for stuff to be fixed upstream and then I'll continue my adventures trying to do this.
j
a
ngl I'm not very good with docker, so I think I'm just going to leave it for now
I might just bypass this issue by moving to a non-ARM VPS x_x
thank you so much for your help tonight
j
No problems. Good luck!
a
thank you
I'm probably going to dig at this more tomorrow
see if I can figure out the network mode thing
j
No worries. It's pretty simple. I think it goes at the root level of the docker compose
a
gotcha
I'll have to upgrade postgres though, I'm currently running on 12.
j
a
Do you think I could just put that under 
db
then, or would I need to pass it to every single one of the services?
j
Every single one of the other services
And comment out db
You'd probably also need to provide and external services note. Might be a bit much for one night of debugging haha
a
probably x_x
I'll try it in the morning, I suppose
Having thoroughly tried this... I guess I just gotta wait for the ARM postgres container to be available.
j
No worries 🙂
k
+1 waiting
j
@Kamyker You're better off just subscribing to updates in the github issues
PreviousNext
Powered by