Bobbie Soedirgo

Unfortunately no, the image would have to be fixed first 😕

@micahburnside yeah, I think the root cause is the same - most of these containers require db connection to work.

Yeah sorry, the whole picture isn't very clear right now. Some of the services e.g. the auth server (GoTrue) needs a db connection because it stores the users table etc....

@saendu your list above looks right - we had to temporarily remove linux/arm64 support for supabase/postgres because the builds were prohibitively slow in GitHub Actions. linux/arm64 images for earlier versions...

It's mainly because GitHub Actions hosted runners don't support linux/arm64. Builds are then done using qemu, but that led to timeouts: https://github.com/supabase/postgres/actions/runs/2035257755

Yeah, we use GitHub Actions to build our images. Open to alternatives for linux/arm64 images.

It took a while, but we now have an [arm64 build](https://hub.docker.com/r/supabase/postgres/tags) for supabase/postgres! 🎉

I think the motivation to use `uuid-ossp` is because we have user DBs which are still on PG12 (native uuid is 13+ afaik) - once we obsolete PG12, we can...

You can also use the `DOCKER_HOST` env for now (in `~/.bashrc`, etc.) until this is fixed upstream: ```sh DOCKER_HOST=unix:///Users/me/.docker/run/docker.sock supabase start ```

We're working on an updated docs for TypeScript support. openapi-typescript isn't compatible with supabase-js v2.