[pkg-go] Bug#1121681: Future podman metadata backend deprecation/migration (nag message)

[Jan Binder]

Am Mittwoch, 3. Dezember 2025, 02:34:29 Mitteleuropäische Normalzeit schrieb 
Reinhard Tartler:
> Jan Binder <jb-debbugs at nlogn.org> writes:
> > documenting this upcoming issue is a good first step.
> > 
> > I have a hard time judging how generally applicable the tool for
> > semaphoreui boltdb to sqlite migration is, I thought it was mentioned
> > more as an example of how such a migration might be done in general.
> 
> Agreed, it is a starting point at best, not a tool that is ready to use
> at this point.
> 
> > In my specific case, everything except the volumes and their contents
> > is easily recreated from podman-compose.
> 
> I wonder what's the story around data backups for those volumes?

Backup is basically just snapshotting /var and pushing the snapshot offsite, 
assuming that everything will be back in the same state when restoring the 
snapshot. Container pull/updates are done after backups.

I guess if the metadata storage and by extension named (non-bind-mounted) 
volumes are considered disposable, I should really change my setup to not use 
them and get rid of the migration issue that way.


Best,
Jan