DEV Community

loading...

Discussion on: Explain like I'm five: How does docker application update work?

Collapse
theodesp profile image
Theofanis Despoudis

There are a few strategies here but docker is just a vessel. You would perform the same steps as if you didn’t use docker. For example you would create a new image with the latest Postgres and import the database dump from the existing database.Assuming they are compatible and there are no breaking changes you could roll out the new container

Collapse
marcel_cremer profile image
Marcel Cremer Author

Hey,

thank you for your answer.

There are a few strategies here but docker is just a vessel. You would perform the same steps as if you didn’t use docker

that basically means I would have to

  • shutdown the container
  • install a local postgresql database service in the old version
  • mount the database
  • run the upgrade installer which updates the database files to the current version
  • start a container with the new version having mounted the updated database files

For every Environment that was deployed?

Isn't that the point where every developer wants to shoot himself, if he ever brought up docker to the table?

Assuming they are compatible and there are no breaking changes you could roll out the new container

I'm coming from IT Service Management (Patch Management, Software deployment and so on) and pretty much every application does something in their update scripts (which is, of course, why they exist), that's why this sounds really shocking to me...

Collapse
frosnerd profile image
Frank Rosner

For every Environment that was deployed?

Isn't that the point where every developer wants to shoot himself, if he ever brought up docker to the table?

I guess that's the point where you should think about either automating the work or using a managed DB. You could of course also attempt to modify the existing container and save the state but that kind of defeats the purpose of Docker.