got collation warning after pull of latest postgres:17

I was using for some persisted test database postgres:17 image

After the most recent pull of the image and restart, I got for a persisted db:
DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

I assume this is due to postgres:17 moved to using debian trixi, as after restarting with image postgres:17-bookworm no more warnings are displayed.
(hostsystem is bullseye, maybe also related)

I do know that latest images are almost always not a good idea, but somehow I always associated this to the main application, not an underlying change of os system used in a Dockerfile.

But ok, my bad.
I only reported this so others are aware. If confirmed, and not my error, then maybe a warning on the main info page on https://hub.docker.com/_/postgres will help others.

Start by reviewing the postgres Docker Official Image page at https://hub.docker.com/_/postgres and compare the postgres:17 and postgres:17-bookworm image notes. Confirm whether the Debian base-image change causes the collation warning, then document the warning and the affected persisted-database scenario on the main image page.