The postgis/postgis image provides tags for running Postgres with PostGIS extensions installed. This image is based on the official postgres image and provides debian and alpine variants for PostGIS both 2.5.x and 3.2.x for each supported version of Postgres (10, 11, 12, 13 and 14). Additionally, an image version is provided which is built from the latest two versions of Postgres (13, 14) with versions of PostGIS and its dependencies built from their respective master branches.

This image ensures that the default database created by the parent postgres image will have the following extensions installed:

• postgis
• postgis_topology
• postgis_tiger_geocoder

Note: As of PostGIS v3.x, raster has been factored out into a separate extension postgis_raster which must be installed separately.

Unless -e POSTGRES_DB is passed to the container at startup time, this database will be named after the admin user (either postgres or the user specified with -e POSTGRES_USER). If you would prefer to use the older template database mechanism for enabling PostGIS, the image also provides a PostGIS-enabled template database called template_postgis.

Recomended version for the new users: postgis/postgis:14-3.2

• It's conservative in its release cycle to ensure high stability.
  • "conservative" ~= not the latest geos, proj, gdal packages.
• Postgis, geos, proj, gdal packages from debian repository
  • debian:bullseye : geos=3.9; gdal=3.2; proj=7.2
  • debian:stretch : geos=3.7; gdal=2.1; proj=4.9
• Easy to extend, matured

• base os = Alpine linux: designed to be small, simple and secure ; musl libc based
• alpine:3.16 and Postgis 2.5:
  • geos=3.8; gdal=3.2; proj=7.2
• alpine:3.16 and Postgis 3.2:
  • geos=3.10; gdal=3.5; proj=9.0
• Postgis has been compiled from source ; harder to extend
• no SFCGAL support yet; (postgis_sfcgal is not working )

• alpha, beta and not released versions
• the *-master images template manually updating, so sometimes you can expact a few weeks delay.

In order to run a basic container capable of serving a PostGIS-enabled database, start a container as follows:

docker run --name some-postgis -e POSTGRES_PASSWORD=mysecretpassword -d postgis/postgis

For more detailed instructions about how to start and control your Postgres container, see the documentation for the postgres image here.

Once you have started a database container, you can then connect to the database either directly on the running container:

docker exec -ti some-postgis psql -U postgres

... or starting a new container to run as a client. In this case you can use a user-defined network to link both containers:

docker network create some-network

# Server container
docker run --name some-postgis --network some-network -e POSTGRES_PASSWORD=mysecretpassword -d postgis/postgis

# Client container
docker run -it --rm --network some-network postgis/postgis psql -h some-postgis -U postgres

Check the documentation on the postgres image and Docker networking for more details and alternatives on connecting different containers.

See the PostGIS documentation for more details on your options for creating and using a spatially-enabled database.

When You encouter errors due to PostGIS update OperationalError: could not access file "$libdir/postgis-X.X, run:

docker exec some-postgis update-postgis.sh

It will update to Your newest PostGIS. Update is idempotent, so it won't hurt when You run it more than once, You will get notification like:

Updating PostGIS extensions template_postgis to X.X.X
NOTICE:  version "X.X.X" of extension "postgis" is already installed
NOTICE:  version "X.X.X" of extension "postgis_topology" is already installed
NOTICE:  version "X.X.X" of extension "postgis_tiger_geocoder" is already installed
ALTER EXTENSION
Updating PostGIS extensions docker to X.X.X
NOTICE:  version "X.X.X" of extension "postgis" is already installed
NOTICE:  version "X.X.X" of extension "postgis_topology" is already installed
NOTICE:  version "X.X.X" of extension "postgis_tiger_geocoder" is already installed
ALTER EXTENSION