6 steps for migrating a PostgreSQL database between containers
Upgrading your container-based database? Keep the process straightforward using these steps.
I decided to run Kanboard, an open source project management application, in a rootless Podman pod as a small weekend project. The pod consists of three containers, an infra-container, a kanboard-container, and a postgresql-container. That deployment went well, but eventually, the image I used for the postgresql-container became deprecated, meaning it was no longer receiving updates. It was time to move to a different image, but that meant migrating a database between containers. It sounds intimidating, but the process is actually straightforward. Here's how to do it.
Migrate to an upgraded PostgreSQL
The process for migrating a database in containers is mostly the same as it is for any other database, but with an additional step to manage containers. Here's an outline of the steps I took:
- Back up the current database.
- Stop and remove the container.
- Delete the directory and files of the old PostgreSQL version from the Podman volume.
- Move the SQL dump file to the Podman volume.
- Start the pod with the rhel8/postgresql-13 container.
- Restore the database.
[ Download the Bash shell scripting cheat sheet. ]
Here are the steps broken down.
First, back up the database:
$ podman exec -t [container name] \ /usr/bin/pg_dump [database name] > dump.sql
Next, empty the Podman volume of the database:
$ podman volume inspect [volume name] $ sudo rm -rf \ ~/.local/share/containers/storage/volumes/[volume name]/_data/*
Now move the database dump to the Podman volume:
$ mv dump.sql \ ~/.local/share/containers/storage/volumes/[volume name>]/_data/
Note: be sure to start the postgresql-cotainer using the new container image rhel8/postgresql-13:
$ podman run -d --pod [pod name] --name [container name] \ -e POSTGRESQL_USER=root \ -e POSTGRESQL_PASSWORD=SecretPassword \ -e POSTGRESQL_DATABASE=[database name] \ -v [volume name]:/var/lib/pgsql/data:Z rhel8/postgresql-13
And finally, restore the database to the container:
$ podman exec -it [container name] bash $ psql -U [user name] -d [database name] \ < /var/lib/pgsql/data/dump.sql
Give it a try
Migrating to a new database release in containers is not difficult when you know the steps. I also think you can apply these procedures to other databases that run in containers.
Haven't started your container journey yet? Well, you might begin with Alexon Oliveira's article on Podman scripting.
While you can't—and shouldn't—use sudo with rootless Podman, there are workarounds.
Learn what's happening in the world of containers and how to better manage this technology.
A home lab is a great way to get started with containers, an essential component in today's IT landscape.