-
-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
supabase start service not healthy : [supabase_edge_runtime_chatbotui supabase_pg_meta_chatbotui supabase_studio_chatbotui] #2146
Comments
Based on this SO post, it could be an issue with nodejs exceeding the user process limit of your host OS, which is inherited by docker container. What's your output from running ulimit? $ ulimit
unlimited |
I have this same issue.... running ulimit:
Any other ideas? |
I can seem to reproduce this on gitpod which runs ubuntu 22.04. I noticed that chatbot-ui doesn't use edge functions, so it would be ok to exclude it from starting. supabase start -x edge-runtime Could you share the logs again after running the above command? |
`🥳 >supabase start -x edge-runtime
✓ Ready in 311ms
✓ Ready in 389ms
▲ Next.js 14.1.4
✓ Ready in 294ms
▲ Next.js 14.1.4
▲ Next.js 14.1.4
✓ Ready in 272ms
✓ Ready in 260ms |
I reinstalled docker and it now works! |
Describe the bug
supabase start
service not healthy : [supabase_edge_runtime_chatbotui supabase_pg_meta_chatbotui supabase_studio_chatbotui]
To Reproduce
Steps to reproduce the behavior:
Go to run supabase start and logs:
Applying migration 20240108234540_setup.sql...
Applying migration 20240108234541_add_profiles.sql...
Applying migration 20240108234542_add_workspaces.sql...
Applying migration 20240108234543_add_folders.sql...
Applying migration 20240108234544_add_files.sql...
Applying migration 20240108234545_add_file_items.sql...
Applying migration 20240108234546_add_presets.sql...
Applying migration 20240108234547_add_assistants.sql...
Applying migration 20240108234548_add_chats.sql...
Applying migration 20240108234549_add_messages.sql...
Applying migration 20240108234550_add_prompts.sql...
Applying migration 20240108234551_add_collections.sql...
Applying migration 20240115135033_add_openrouter.sql...
Applying migration 20240115171510_add_assistant_files.sql...
Applying migration 20240115171524_add_tools.sql...
Applying migration 20240115172125_add_assistant_tools.sql...
Applying migration 20240118224049_add_azure_embeddings.sql...
Applying migration 20240124234424_tool_improvements.sql...
Applying migration 20240125192042_upgrade_openai_models.sql...
Applying migration 20240125194719_add_custom_models.sql...
Applying migration 20240129232644_add_workspace_images.sql...
Applying migration 20240212063532_add_at_assistants.sql...
Applying migration 20240213040255_remove_request_in_body_from_tools.sql...
Applying migration 20240213085646_add_context_length_to_custom_models.sql...
Applying migration 20240302004845_add_groq.sql...
Seeding data supabase/seed.sql...
supabase_edge_runtime_chatbotui container logs:
if run supabase start --ignore-health-check
...
service not healthy: [supabase_edge_runtime_chatbotui supabase_pg_meta_chatbotui supabase_studio_chatbotui]
Started supabase local development setup.
and run supabase status :
supabase_pg_meta_chatbotui container is not ready: unhealthy
supabase_studio_chatbotui container is not ready: unhealthy
Stopped services: [supabase_analytics_chatbotui]
supabase local development setup is running.
$docker ps -a | grep supabase
acf23d9b413a public.ecr.aws/supabase/edge-runtime:v1.41.3 "edge-runtime" 38 minutes ago Exited (139) 38 minutes ago supabase_edge_runtime_chatbotui
52b8080856ed public.ecr.aws/supabase/studio:20240326-5e5586d "docker-entrypoint.s…" 43 minutes ago Restarting (139) 4 seconds ago supabase_studio_chatbotui
20bb1d050ad5 public.ecr.aws/supabase/postgres-meta:v0.80.0 "docker-entrypoint.s…" 43 minutes ago Restarting (139) 32 seconds ago
Expected behavior
supabase start runing ok.
Screenshots
supabase start now Three containers are found to be abnormal.
System information
Rerun the failing command with
--create-ticket
flag.The text was updated successfully, but these errors were encountered: