From cf0019e3ed63632fa733dc06d0a2ea70e4c4ea8f Mon Sep 17 00:00:00 2001 From: Paul Holzinger Date: Tue, 10 Mar 2026 13:48:55 +0100 Subject: [PATCH] docs: make the --migrate-db more clear 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 --- docs/source/markdown/podman-system-migrate.1.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/source/markdown/podman-system-migrate.1.md b/docs/source/markdown/podman-system-migrate.1.md index 96d5202f53..213bb7219b 100644 --- a/docs/source/markdown/podman-system-migrate.1.md +++ b/docs/source/markdown/podman-system-migrate.1.md @@ -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*