Handling data volumes over time


Currently I try to understand how to handle database schema upgrades on dockerized applications.

Because initialize a datavolumes works well with an application with bigger database schemas but what happens when there is a version change and a database upgrade?

How do you manage that? Running an own “bootstrap container”? Or run the bootstrap on every start of your application?

I don’t see any other way but may you? Would be nice if you share your experience with those problems

Best regards

What specifically are you struggling with?

A running database could be patched by running another container on the same docker network (or sharing a socket via docker volume), connecting to the database container, and applying the relevant SQL commands / code.

1 Like