Usage
uc remove, uc delete, uc service rm, uc service remove, uc service delete
Arguments
Names or IDs of services to remove. Can specify multiple services.
Examples
Remove a service
Remove multiple services
What Gets Removed
When you remove a service:- Containers - All service containers are stopped and removed
- Service configuration - Service metadata is removed
- Anonymous volumes - Automatically created volumes from Dockerfile
VOLUMEdirectives
What’s Preserved
These are NOT removed:- Named volumes - Must be removed separately with
uc volume rm - Images - Container images remain on machines
- Networks - Cluster network configuration is unchanged
Output
Volumes
Named Volumes
Named volumes used by the service are preserved:Anonymous Volumes
Anonymous volumes (created automatically fromVOLUME directives in Dockerfiles) are removed with their containers:
Removing vs Stopping
uc rm SERVICE- Permanently removes the service and containersuc stop SERVICE- Temporarily stops containers, preserves everything
uc stop if you might want to start the service again:
uc rm when you’re done with the service:
Redeploying After Removal
To redeploy a removed service:Use Cases
Clean Up Old Services
Remove services you no longer need:Redeploy from Scratch
Remove and redeploy to ensure clean state:Free Up Resources
Remove services to free up CPU and memory:Important Notes
Data Loss Warning
Removing a service deletes containers and their data. Make sure important data is in volumes:Cannot Undo
Once removed, you cannot bring the service back withuc start. You must redeploy:
Related Commands
uc service stop- Stop services without removinguc service start- Start stopped servicesuc service ls- List servicesuc volume rm- Remove volumesuc deploy- Redeploy services
