This page outlines how and when images are built and pushed to Docker Hub.
The PgOSM Flex Docker image uses main Postgres image via the main PostGIS image as starting point. Those repositories have detailed instructions on using and customizing the core Postgres functionality.
There are three main types of images pushed to Docker Hub.
Which branch is best for you depends on how you use the data from PgOSM Flex.
Tagged releases are the most stable option and are recommended if you are
Tagged releases are built with the latest versions of all key software, e.g. Postgres,
PostGIS and osm2pgsql, and their dependencies. These tagged images (e.g.
are typically built at the time the tag is added to GitHub, and are (typically)
PgOSM Flex is still evolving on a regular basis. This means new tagged releases are coming out as activity happens in the project.
If you run PgOSM Flex without
--update mode this image is
generally stable and includes the latest features.
latest Docker image could include changes that
require manual changes in Postgres. Those changes are documented in the release notes,
for example, see "Notes for
--append users" in 0.6.1 release notes.
dev image exists when there's something worth testing. Typically the
image is deleted from Docker Hub as functionality is worked into the
Build latest. Occasionally run with
--no-cache to force some software updates.
docker build -t rustprooflabs/pgosm-flex .
Tag with version.
docker build -t rustprooflabs/pgosm-flex:0.10.0 .
Push to Docker Hub.
docker push rustprooflabs/pgosm-flex:latest docker push rustprooflabs/pgosm-flex:0.10.0
To be certain the latest images are being used and latest
software is installed, pull the latest PostGIS image and build
the PgOSM Flex image using
docker pull postgis/postgis:16-3.4 docker build --no-cache -t rustprooflabs/pgosm-flex:dev .