opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2026-03-13 08:01:19 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: make the --migrate-db more clear

Browse Source 
Recommend the reboot option instead if users cannot shut down all podman
commands. Also update the wording that users MUST shut down commands for
correct migration.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This commit is contained in:
Paul Holzinger
2026-03-10 13:48:55 +01:00
parent 5dcc24d01d
commit cf0019e3ed
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/source/markdown/podman-system-migrate.1.md
View File

@@ -31,9 +31,11 @@ newly configured mappings.
Migrate from the legacy BoltDB database to SQLite.
Support for BoltDB will be removed in Podman 6.0.
Podman will display a warning if this migration is necessary.
To ensure complete migration, all other Podman commands should be shut down before database migration.
To ensure complete migration, all other Podman commands must be shut down before database migration.
In particular, systemd-activated services like **podman system service** and Quadlets should be manually stopped prior to migration.
The legacy database will not be removed, so no data loss should occur even on failure.
If you are unsure please reboot instead and run any podman command afterwards which will trigger the migration
automatically as we can ensure there that no other parallel commands can interfere with the database.
The legacy database will not be removed, just renamed, so no permanent data loss should occur even on failure.
#### **--new-runtime**=*runtime*