Every mkdb container has a time to live (TTL) — a countdown that starts when the container is created and ends when the container is automatically removed. TTL exists to prevent stale development databases from accumulating on your machine. When a container’s TTL expires, mkdb stops and deletes it along with its volume. You can configure the TTL at creation time and extend it later if you need more time.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.
Default TTL
The default TTL is 2 hours. If you do not specify--ttl when creating a database, mkdb sets the expiration to 2 hours from the time of creation.
Setting TTL at creation
Pass--ttl with a number of hours when running mkdb start:
| Hours | Use case |
|---|---|
1 | Short-lived test database |
2 | Default — quick development session |
48 | Two-day development session |
168 | One-week long-running database |
Extending TTL
If a container is still running and you need more time before it expires, usemkdb extend to add hours to its remaining TTL:
--hours flag defaults to 1 if omitted:
What happens when TTL expires
When a container’s TTL reaches zero:- The container is stopped and removed from Docker.
- The volume is permanently deleted, including all data it contains.
- The container record is removed from the mkdb database.