supabase: It wont start on macos with docker compose

Bug report

When I run the docker compose up -d docker will initialize all the images but it will fail to run.

specially meta and studio.

Screen Shot 2024-01-10 at 10 27 41 PM

then on the browser I will get

{
"message": "name resolution failed"
}

meta docker log

2024-01-10 22:27:43 (node:19) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
2024-01-10 22:27:43 Segmentation fault
2024-01-10 22:27:56 Segmentation fault
2024-01-10 22:28:22 Segmentation fault
2024-01-10 22:29:14 (node:19) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
2024-01-10 22:29:14 (Use `node --trace-warnings ...` to show where the warning was created)
2024-01-10 22:29:14 Segmentation fault
2024-01-10 22:30:14 Segmentation fault
2024-01-10 22:27:56 > node dist/server/server.js

studio docker log

2024-01-10 22:28:24  ✓ Ready in 253ms
2024-01-10 22:29:16   ▲ Next.js 13.5.3
2024-01-10 22:29:16   - Local:        http://a0924904c358:3000
2024-01-10 22:29:16   - Network:      http://172.21.0.11:3000
2024-01-10 22:29:16 
2024-01-10 22:29:16  ✓ Ready in 253ms
2024-01-10 22:30:17   ▲ Next.js 13.5.3
2024-01-10 22:30:17   - Local:        http://a0924904c358:3000
2024-01-10 22:30:17   - Network:      http://172.21.0.11:3000
2024-01-10 22:30:17 
2024-01-10 22:30:17  ✓ Ready in 350ms

I confirm this is a bug with Supabase, not with my own application.
I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Won’t run with initial setup

To Reproduce

# Get the code
git clone --depth 1 https://github.com/supabase/supabase

# Go to the docker folder
cd supabase/docker

# Copy the fake env vars
cp .env.example .env

# Pull the latest images
docker compose pull

# Start the services (in detached mode)
docker compose up -d

Expected behavior

Able to see the landing page with localhost:8000

Screenshots

If applicable, add screenshots to help explain your problem.

System information

OS: macOS 12.6
Browser (if applies) [e.g. chrome, safari]
Version of supabase-js: latest from the repo - (package.json was never updated “version”: “0.0.0”,)
Version of Node.js: using docker.

Additional context

I am using docker desktop version 4.26.1 (131620) Using virtualization framework with gRPC FUSE(got this from one of git issue tread)

About this issue

Original URL
State: closed
Created 6 months ago
Reactions: 2
Comments: 19 (6 by maintainers)

Most upvoted comments

actually I was wrong even on ubuntu I am getting

NAME                             IMAGE                              COMMAND                   SERVICE     CREATED         STATUS                     PORTS
realtime-dev.supabase-realtime   supabase/realtime:v2.25.50         "/usr/bin/tini -s -g…"    realtime    8 minutes ago   Up 8 minutes (healthy)
supabase-analytics               supabase/logflare:1.4.0            "sh run.sh"               analytics   8 minutes ago   Up 8 minutes (healthy)     0.0.0.0:4000->4000/tcp, :::4000->4000/tcp
supabase-auth                    supabase/gotrue:v2.132.3           "auth"                    auth        8 minutes ago   Up 8 minutes (healthy)
supabase-db                      supabase/postgres:15.1.0.147       "docker-entrypoint.s…"    db          8 minutes ago   Up 8 minutes (healthy)     0.0.0.0:5432->5432/tcp, :::5432->5432/tcp
supabase-edge-functions          supabase/edge-runtime:v1.29.1      "edge-runtime start …"    functions   8 minutes ago   Up 8 minutes
supabase-imgproxy                darthsim/imgproxy:v3.8.0           "imgproxy"                imgproxy    8 minutes ago   Up 8 minutes (healthy)     8080/tcp
supabase-kong                    kong:2.8.1                         "bash -c 'eval \"echo…"   kong        8 minutes ago   Up 8 minutes (healthy)     8001/tcp, 8444/tcp, 0.0.0.0:8443->8443/tcp, :::8443->8443/tcp, 0.0.0.0:8888->8000/tcp, :::8888->8000/tcp
supabase-meta                    supabase/postgres-meta:v0.75.0     "docker-entrypoint.s…"    meta        8 minutes ago   Up 8 minutes (healthy)     8080/tcp
supabase-rest                    postgrest/postgrest:v12.0.1        "postgrest"               rest        8 minutes ago   Up 8 minutes               3000/tcp
supabase-storage                 supabase/storage-api:v0.43.11      "docker-entrypoint.s…"    storage     8 minutes ago   Up 8 minutes (healthy)     5000/tcp
supabase-studio                  supabase/studio:20240101-8e4a094   "docker-entrypoint.s…"    studio      8 minutes ago   Up 8 minutes (unhealthy)   3000/tcp
supabase-vector                  timberio/vector:0.28.1-alpine      "/usr/local/bin/vect…"    vector      8 minutes ago   Up 8 minutes (healthy)

supabase-studio supabase/studio:20240101-8e4a094 “docker-entrypoint.s…” studio 8 minutes ago Up 8 minutes (unhealthy)

Also when I do able to see the UI and create a schema I get an error

Failed to create schema: Connection string is required

similar to add an user

Failed to create user: An error has occurred: Failed to fetch

I am running this under proxmox ubuntu VM with sse4_2 enabled.

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         40 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               GenuineIntel
  Model name:            Intel Core Processor (Skylake)
    CPU family:          6
    Model:               94
    Thread(s) per core:  1
    Core(s) per socket:  8
    Socket(s):           1
    Stepping:            3
    BogoMIPS:            8015.96
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat ps
                         e36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc r
                         ep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma
                         cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes x
                         save avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_faul
                         t invpcid_single pti fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid r
                         tm rdseed adx smap xsaveopt xsavec xgetbv1 arat
Virtualization features:
  Hypervisor vendor:     KVM
  Virtualization type:   full
Caches (sum of all):
  L1d:                   256 KiB (8 instances)
  L1i:                   256 KiB (8 instances)
  L2:                    32 MiB (8 instances)
  L3:                    16 MiB (1 instance)
NUMA:
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:
  Gather data sampling:  Not affected
  Itlb multihit:         KVM: Mitigation: VMX unsupported
  L1tf:                  Mitigation; PTE Inversion
  Mds:                   Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host stat
                         e unknown
  Meltdown:              Mitigation; PTI
  Mmio stale data:       Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host stat
                         e unknown
  Retbleed:              Vulnerable
  Spec rstack overflow:  Not affected
  Spec store bypass:     Vulnerable
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not
                          affected
  Srbds:                 Unknown: Dependent on hypervisor status
  Tsx async abort:       Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host stat
                         e unknown

incase you need this info

tyou0 on Jan 23, 2024

thanks @encima Got it working by turning off the virtualization framework.

justinboynton on Apr 1, 2024

Confirmed. I’m facing the exact same problem.

It’s a fresh install, and here’s what I’m getting when I run supabase start

...
> @supabase/postgres-meta@0.0.0-automated start
> node dist/server/server.js

Segmentation fault

service not healthy: [supabase_pg_meta_<project name> supabase_studio_<project name>]

I’m using Mac OS Sonoma 14.1

vvinhas on Jan 12, 2024

This was my first time installing it, but I will give it a try again.

tyou0 on Jan 11, 2024