Skip to main content

​
Stop Buster Services

The buster stop command gracefully shuts down all running Buster services that were started with the buster start command. This frees up system resources when you’re not actively using Buster.

​
Basic Usage

buster stop
The stop command has no additional options.

​
What It Does

When you run buster stop, the following happens:
  1. Identifies the Docker Compose configuration in your ~/.buster directory
  2. Runs docker compose down to stop and remove all containers
  3. Preserves all data and configuration for the next start
This is a clean shutdown that:
  • Stops all Buster service containers
  • Removes the containers from memory
  • Maintains all data volumes and configuration files
  • Allows for a clean restart later

​
Example Output

Stopping Buster services...

Buster services stopped successfully.

​
Data Persistence

The stop command only stops the running services. It does not:
  • Delete any data in your database
  • Remove configuration files
  • Delete Docker images
  • Remove Docker volumes
All your data and settings are preserved for the next time you run buster start.

​
When to Use

You should use buster stop when:
  • You’re done using Buster for the day
  • You need to free up system resources
  • You want to clean up running containers
  • Before shutting down your computer
  • Before running buster reset if you want a clean reset

​
Troubleshooting

If you encounter issues with the stop command:
  • Services still running: Check Docker status with docker ps
  • Permission issues: Ensure you have the necessary permissions to manage Docker
  • Directory not found: Ensure you’ve previously run buster start

​
Common Use Cases

​
Daily Development Workflow

# Start Buster in the morning
buster start

# Work with Buster during the day...

# Stop Buster at the end of the day
buster stop

​
Maintenance

# Stop services before maintenance
buster stop

# Perform system maintenance...

# Restart services when done
buster start