Repository navigation
Closed
Labels
Description
Affected area
Local development
Supabase CLI version
v2.114.0
Operating system
Ubuntu 24.04 (in WSL)
Installation method
npm
Command
npx supabase startActual output
NotFound: FileSystem.readFile (/home/user/.supabase/profile)
Starting database...
Stopping containers...
Pruned containers: [266fa96f6c43f80592d4787a6b1da255422eb50743ce3a41d39d19bb111248ca]
Pruned volumes: [supabase_db_myproject]
Pruned network: [supabase_network_myproject]
failed to create docker container: failed to copy secret file into container: lstat /tmp/supabase-start-secret-RSf80t: no such file or directoryExpected behavior
I expected Supabase to stand up its local development environment.
Steps to reproduce
In a bare directory, run:
- supabase init
- supabase start
The error appears as soon as the docker infrastructure is created.
Crash report ID
No response
Docker and service versions
`docker version`:
Client:
Version: 29.6.1
API version: 1.55
Go version: go1.26.5
Git commit: 8900f1d
Built: Thu Jul 16 20:08:21 2026
OS/Arch: linux/amd64
Context: default
Server:
Engine:
Version: 29.6.1
API version: 1.55 (minimum version 1.40)
Go version: go1.26.5
Git commit: 8ec5ab3
Built: Thu Jul 16 20:09:02 2026
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.3.3
GitCommit: aad11006b869517fcd3009450b6f82da282e1a9b
runc:
Version: 1.5.1
GitCommit:
docker-init:
Version: 0.19.0
GitCommit: de40ad0
`supabase services`:
SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|--------
supabase/postgres | 17.6.1.158 | -
supabase/gotrue | v2.195.0 | -
postgrest/postgrest | v16.1 | -
supabase/realtime | v2.124.4 | -
supabase/storage-api | v1.69.0 | -
supabase/edge-runtime | v1.74.3 | -
supabase/studio | 2026.08.10-sha-5b68af1 | -
supabase/postgres-meta | v0.97.0 | -
supabase/logflare | 1.50.2 | -
supabase/supavisor | 2.9.7 | -Additional context
I can't think of anything unusual about this setup except that it's running in WSL. I installed docker via sudo snap install docker and added myself to the docker group, other than that nothing weird on this environment.
Activity
fix(cli): stream container secrets (CLI-2190) (supabase#6201)
CalvinWilkinson commentedon Nov 12, 2026
@7ttp
Just FYI. This happens and is a problem when using Podman v5.8.9 as well.
7ttp commentedon Nov 12, 2026
thanks for the heads up! 💚
I couldn’t reproduce this with podman on my end though
could you open a new issue w a bit more detail? thanks!