Reset Buster Services
Thebuster reset
command performs a complete reset of your local Buster environment. This is useful when you want to start with a clean installation or resolve issues with your current setup.
Basic Usage
What It Does
The reset command performs these steps:- Stops all Buster services: Shuts down all running Docker containers
- Removes Docker images: Deletes the Docker images used by Buster
- Wipes the
~/.buster
directory: Removes all configuration files and data - Preserves credentials: Keeps only your
credentials.yml
file if it exists
Confirmation Required
Because this is a destructive operation, the command requires explicit confirmation:y
to confirm the reset. Any other input will cancel the operation.
Reset Process Details
The reset operation has three main phases:-
Service Shutdown Phase:
- Stops all Docker containers using
docker compose down
- Reports any issues but continues with the reset process
- Stops all Docker containers using
-
Image Removal Phase:
- Identifies all Docker images used by Buster
- Removes each image individually
- Reports the status of each image removal
-
Directory Cleanup Phase:
- Backs up the
credentials.yml
file if it exists - Removes the entire
~/.buster
directory - Creates a fresh
~/.buster
directory - Restores the backed-up credentials file
- Backs up the
When to Use Reset
You should consider using the reset command when:- Your Buster installation is not working correctly
- You want to start with a clean environment
- You’ve made configuration changes that caused problems
- You want to clear all data and start fresh
- Docker-related issues prevent normal operation
After Resetting
After a successful reset, you need to runbuster start
to rebuild your Buster environment. This will:
- Extract all necessary files to the newly created
~/.buster
directory - Prompt for any required configuration (API keys, etc.)
- Download and build Docker images
- Start all Buster services in a fresh state
Troubleshooting
If you encounter issues with the reset command:- Permission errors: Ensure you have permission to manage Docker and write to the
~/.buster
directory - Docker issues: Check if Docker is running properly
- Locked files: Close any applications that might be accessing files in the
~/.buster
directory