docker-compose.yml point to wrong image tags at on CE server releases #540

Activity

1. MarcelGeo commented on Nov 28, 2025

   

   MarcelGeo

   on Nov 28, 2025

   Collaborator

   More actions

   Hi @davd-edia, we've already updated the current tag for the 2025.7.3 images. Sometimes these docker-compose files are developed and fixed after the tag is created.

   Follow the documentation here here on how to upgrade from 2025.2.2 to 2025.7.3 (latest version) and here here on what changed between 2024 and 2025.2.2.

   The best way is to update the docker-compose files from the master branch. Review what has changed between your versions (checking for any breaking changes to deployment, env variables, etc.) in the migration docs and then run the database migration defined in you 2024 version, which will move your database from 2024 to 2025.7.3.

   Check that you are on correct versions (35af0c8be41e, a5d4defded55).
   
   $ docker exec merginmaps-server flask db current
   INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
   INFO  [alembic.runtime.migration] Will assume transactional DDL.
   35af0c8be41e (head)
   a5d4defded55
   
       If you do not see the version numbers at all, run the following commands:
   
   $ docker exec merginmaps-server flask db stamp 35af0c8be41e
   $ docker exec merginmaps-server flask db stamp a5d4defded55
   
   Run the database migration (this will move you to latest version):
   
   $ docker exec merginmaps-server flask db upgrade heads
   

   Any other questions?
2. davd-edia commented on Nov 28, 2025

   

   davd-edia

   on Nov 28, 2025

   Author

   More actions

   That's all. Thanks.

   👍React with 👍1Reacted by Marcel Kocisek
3. MarcelGeo

   closed this as completedon Dec 4, 2025