Calling supabase stop doesn't affect on running containers#10
Merged
Conversation
OS: Ubuntu 20.04 LTS **Issue**: Calling `supabase stop` doesn't affect on running containers. *supabase start*: docker-compose --file .supabase/docker/docker-compose.yml --project-name supabase up -d > Creating network "supabase_default" with the default driver Creating supabase-db ... done Creating supabase-kong ... done Creating supabase-auth ... done Creating supabase-realtime ... done Creating supabase-rest ... done *supabase down* with current command: docker-compose --file .supabase/docker/docker-compose.yml down > Removing network docker_default WARNING: Network docker_default not found. *supabase down* fix: docker-compose --file .supabase/docker/docker-compose.yml **--project-name supabase** down > Stopping supabase-realtime ... done Stopping supabase-rest ... done Stopping supabase-auth ... done Stopping supabase-kong ... done Stopping supabase-db ... done Removing supabase-realtime ... done Removing supabase-rest ... done Removing supabase-auth ... done Removing supabase-kong ... done Removing supabase-db ... done Removing network supabase_default
Member
|
🔥 thanks for the help @any-me |
|
🎉 This PR is included in version 0.3.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
dumko2001
pushed a commit
to dumko2001/cli
that referenced
this pull request
Mar 15, 2026
kallebysantos
pushed a commit
to kallebysantos/supabase-cli
that referenced
this pull request
May 6, 2026
## What kind of change does this PR introduce? Switch to `pnpm` as package manager ## What is the current behavior? `bun` is being used as the package manager ## What is the new behavior? `pnpm` is being used as the package manager --------- Co-authored-by: Julien Goux <hi@jgoux.dev>
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OS: Ubuntu 20.04 LTS
Issue: Calling
supabase stopdoesn't affect on running containers.supabase start: docker-compose --file .supabase/docker/docker-compose.yml --project-name supabase up -d
supabase down with current command: docker-compose --file .supabase/docker/docker-compose.yml down
supabase down fix: docker-compose --file .supabase/docker/docker-compose.yml --project-name supabase down