Bug report
Describe the bug
Running supabase offline (ie without an internet connection) fails because somewhere in supabase the system is attempting to download a status.ts file directly from deno.land servers every time the server starts.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Install supabase via npm (in my case, I am using the
bun client)
- Run
supabase start
- After the database has successfully downloaded docker images and started, stop the database with
supabase stop
- Disconnect Internet
- Run
supabase start again
Expected behavior
After running supabase start for the first time locally, the docker files and environment should run in isolation without depending on external resources. Supabase's documentation even states as much.
System information
- OS: macOS
- Docker version 29.4.1, build 055a478
- Version of supabase: 2.98.1
- Version of Node.js: v22.22.0
- Version of NPM: 10.9.4
- Version of Bun.js: 1.3.11
Additional context
Error output Example:
$ supabase start
[+] Pulling 13/13
✔ realtime Skipped - Image is already present locally 0.0s
✔ storage Skipped - Image is already present locally 0.0s
✔ studio Skipped - Image is already present locally 0.0s
✔ mailpit Skipped - Image is already present locally 0.0s
✔ imgProxy Skipped - Image is already present locally 0.0s
✔ pgmeta Skipped - Image is already present locally 0.0s
✔ vector Skipped - Image is already present locally 0.0s
✔ gateway Skipped - Image is already present locally 0.0s
✔ api Skipped - Image is already present locally 0.0s
✔ auth Skipped - Image is already present locally 0.0s
✔ edgeRuntime Skipped - Image is already present locally 0.0s
✔ analytics Skipped - Image is already present locally 0.0s
✔ db Skipped - Image is already present locally 0.0s
Starting database...
Initialising schema...
Seeding globals from roles.sql...
Applying migration 20260505015646_migrate.sql...
WARN: no files matched pattern: supabase/seed.sql
Starting containers...
Waiting for health checks...
[PROJECT] container logs:
worker boot error: failed to bootstrap runtime: failed to create the graph: Import 'https://deno.land/std/http/status.ts' failed: error sending request for url (https://deno.land/std/http/status.ts): client error (Connect): dns error: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
at file:///root/index.ts:1:42
Error: main worker boot error
Caused by:
0: worker boot error
1: failed to bootstrap runtime
2: failed to create the graph
3: Import 'https://deno.land/std/http/status.ts' failed: error sending request for url (https://deno.land/std/http/status.ts): client error (Connect): dns error: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
at file:///root/index.ts:1:42
Stopping containers...
posthog 2026/05/05 14:20:29 WARN: sending request - Post "https://eu.i.posthog.com/batch/": dial tcp: lookup eu.i.posthog.com: no such host
Error status 503:
Try rerunning the command with --debug to troubleshoot the error.
error: script "db:start" exited with code 1
Bug report
Describe the bug
Running supabase offline (ie without an internet connection) fails because somewhere in supabase the system is attempting to download a
status.tsfile directly from deno.land servers every time the server starts.To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
bunclient)supabase startsupabase stopsupabase startagainExpected behavior
After running
supabase startfor the first time locally, the docker files and environment should run in isolation without depending on external resources. Supabase's documentation even states as much.System information
Additional context
Error output Example: