mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-05 00:15:44 +00:00
Merge pull request #29298 from satwiksps/docs-transient-store-volumes
docs: clarify --transient-store behavior with volumes
This commit is contained in:
commit
48a6ef9cdf
1 changed files with 4 additions and 0 deletions
|
|
@ -206,6 +206,10 @@ Enables a global transient storage mode where all container metadata is stored o
|
||||||
This mode allows starting containers faster, as well as guaranteeing a fresh state on boot in case of unclean shutdowns or other problems. However
|
This mode allows starting containers faster, as well as guaranteeing a fresh state on boot in case of unclean shutdowns or other problems. However
|
||||||
it is not compatible with a traditional model where containers persist across reboots.
|
it is not compatible with a traditional model where containers persist across reboots.
|
||||||
|
|
||||||
|
Only the Podman database (container and volume metadata) is stored transiently. Volume data on disk is not affected and persists across reboots. After a reboot, previously created volumes will not appear in **podman volume ls** because their database entries were lost, but the underlying data remains in the volume storage directory. If a container later creates a volume with the same name, it will reuse the existing data. To clean up leftover volume data that is no longer tracked by the database, use **podman system prune --external**.
|
||||||
|
|
||||||
|
It should be used consistently across all Podman commands and not mixed with regular (non-transient) usage within the same environment.
|
||||||
|
|
||||||
Default value for this is configured in `containers-storage.conf(5)`.
|
Default value for this is configured in `containers-storage.conf(5)`.
|
||||||
|
|
||||||
#### **--url**=*value*
|
#### **--url**=*value*
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue