Skip to main content

Documentation Index

Fetch the complete documentation index at: https://test.pzona.fun/llms.txt

Use this file to discover all available pages before exploring further.

mkdb stop and mkdb restart let you pause and resume database containers without losing data. Stopping a container preserves the volume so you can bring it back later. Restarting reconnects to that volume and resumes the container with the same credentials and configuration it had before.

​
mkdb stop

mkdb stop stops a running container and preserves its volume. The data remains intact — use mkdb restart to start it again.

​
Flags

​
--name
string
Name of the container to stop. When provided, mkdb skips the interactive selection menu and stops the named container directly.

​
Examples

Interactive mode — select from a list of running containers:
mkdb stop
Non-interactive mode — stop a named container directly:
mkdb stop --name mydb

​
Stop and restart workflow

A common pattern is to stop a container when you are not actively using it and restart it when you need it again — this preserves data while freeing up the port. 
# Stop the container at the end of a session
mkdb stop --name mydb

# Restart it at the start of the next session
mkdb restart --name mydb
Stopping a container does not delete its volume or reset its TTL. If the container’s TTL expires while it is stopped, the automatic cleanup process will still remove it. Use mkdb extend to add time to the TTL before stopping if needed.