Mark Sapiro wrote:
My point was after you remove the newly minted mailmandb database and then create a new blank one, and import into that, you should then run manage.py migrate to apply any new migrations to the imported database.
Ah, right ... ok, I've done that now, and all's good.
Actually, I've noticed something related. It looks like the mailman-web container runs manage.py as part of its startup procedure in any event.
After the import completes, I start up the mailman-web container and, its logs say this:
mailman-web | Operations to perform: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Applying auth.0012_alter_user_first_name_max_length... OK mailman-web | Applying django_q.0014_schedule_cluster... OK mailman-web | Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK mailman-web | Applying postorius.0014_auto_20210329_2248... OK mailman-web | Applying postorius.0015_auto_20210619_0509... OK mailman-web | Applying postorius.0016_auto_20210810_2157... OK
If the container is restarted again, it shows that there's nothing to do this time:
mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | No migrations to apply.
These latter diagnostics are also what I see if, at this point, I enter the mailman-web container and run "manage.py migrate" explicitly.
I really appreciate the help, thanks so much.