Closed knksmith57 closed 2 months ago
Could be related to https://github.com/supabase/supabase/issues/22518
Also potentially related to #2146
Since the logs were cutoff, I suspect it's due to db health check taking longer than the max timeout of 2 minutes. Could you verify on docker settings page that enough resources is allocated?
Hm, that's interesting. 2 data points for color there:
I just realised that you are trying to run cli inside docker compose. This means the health checks require host network mode to work. For eg.
services:
supabase-cli:
network_mode: "host"
command:
- --debug
- start
- --ignore-health-check
build:
target: supabase-cli
context: .
environment:
- SUPABASE_ACCESS_TOKEN
develop:
watch:
- action: rebuild
path: ./packages/supabase/config.toml
working_dir: ${PWD}/packages/supabase
volumes:
- ./packages/supabase:${PWD}/packages/supabase
- "/var/run/docker.sock:/var/run/docker.sock"
Describe the bug This just started happening after a fresh CLI install. I'm not positive the last time I updated it, but it hasn't been more than a month or so.
Standing up the local stack with a completely clean daemon (no volumes, no networks, no containers) crashes after the postgresql container is created but before everything else comes up. I'm able to grab log output from the db container and it seems like the thing just dies with no apparent explanation.
CLI logs (end of tail):
db container logs:
To Reproduce Steps to reproduce the behavior:
supabase --debug start --ignore-health-check --create-ticket
Note: I'm running the supabase CLI from within a dind container (have been successfully for months now) as part of a Docker Compose stack.
Here's the Dockerfile:
Here's the Docker Compose service definition:
Here's the canned
config.toml
I'm mounting/using:Expected behavior I expect the local stack to come up, including (especially) the postgresql database
Screenshots N/A
System information
42be6c774de241e6851a55e4134d84ab
1.153.1
25.0.3
(via Docker Desktop 4.28.0 (139021))Additional context If applicable, add any other context about the problem here.
v20.11.1.