imresamu/postgis

🚧🔧💡🧹 WIP: Experimental development:

• 🧪🐳 test images (amd64 + arm64) for the users: https://hub.docker.com/r/imresamu/postgis
  • 🧪 internal amd64 only repo: https://hub.docker.com/r/imresamu/postgis-amd64/tags
  • 🧪 internal arm64 only repo: https://hub.docker.com/r/imresamu/postgis-arm64/tags
• 🧪 code: https://github.com/ImreSamu/docker-postgis
• Status: Experimental, under active development

---

🐳🐘🌍 postgis/postgis

https://github.com/imresamu/docker-postgis/workflows/Build%20PostGIS%20images/badge.svg](https://github.com/imresamu/docker-postgis/actions) ![Join the chat at []]([]

Important: Please note that this README document is larger than the 25,000 character limit set by Docker Hub. As a result, the version available on Docker Hub will be trimmed and not complete. For the complete and untrimmed version of the README, it is recommended to visit the project GitHub page: https://github.com/ImreSamu/docker-postgis/blob/master/README.md

The imresamu/postgis image provides tags for running Postgres with PostGIS extensions installed. This image is based on the official https://registry.hub.docker.com/_/postgres/ image and provides debian and alpine variants for PostGIS which is compatible with PostgreSQL versions 13, 14, 15, 16 and 17. Additionally, an image version is provided which is built from the latest two versions of Postgres (16,17) 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:

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.

Versions (2025-12-22)

We provide multi-platform image support for the following architectures:

• amd64: Also known as x86-64.
  • Use --platform=linux/amd64 when specifying the platform.
• arm64: Also known as AArch64.
  • Use --platform=linux/arm64 when specifying the platform.

Notes:

• The arm64 architecture support is still experimental. Please refer to the 'arch' column in the version information to determine whether an arm64 version is available for a specific release.
• We currently do not support 32-bit architectures. Our images are only available for 64-bit architectures.

Build Status

🌟Recommended Versions for New Users

For those new to PostGIS, we recommend the following image versions:

• imresamu/postgis:17-3.5-bookworm: This image includes a minimal setup of PostgreSQL with the PostGIS extension. ( debian bookworm based, easy to extend with debian packages )
• imresamu/postgis:17-recent-bookworm: (experimental) Latest postgis with the latest geos,proj,gdal,sfcgal. ( debian based, extending is complex ! )
• imresamu/postgis:16-3.5-bundle0-bookworm: (experimental) This image includes additional geospatial-related extras along with PostgreSQL and PostGIS.

🥇Debian - bookworm (recommended)

• This Docker-PostGIS version has a cautious release cycle to guarantee high stability.
  • By "cautious", we mean it does not always have the latest versions of geos, proj, gdal, and sfcgal packages.
• We use PostGIS, geos, proj, gdal, and sfcgal packages from the Debian repository. The versions are: geos=3.11, gdal=3.6, proj=9.1, and sfcgal=1.4.
• This version is easy to extend and has matured over time.

📘Debian - Trixie

• We use PostGIS, geos, proj, gdal, and sfcgal packages from the Debian repository.
  • In the Debian Trixie repository, the versions are: geos=3.13, gdal=3.10, proj=9.6, and sfcgal=2.0.
• This version is easy to extend and has matured over time.

🧪Recent ( experimental )

• These images are similar to the debian-based *-master images ( same Dockerfile template ) However, for every build, we use the latest released tag from each library (such as postgis, geos, proj, gdal, cgal, sfcgal).
• These images are ideal for testing purposes, but expanding them is not straightforward.
• The specific versions of the libraries used (like postgis, geos, proj, gdal, cgal, sfcgal) can be found in the tags of the image or in the Dockerfile.

🧪Debian Geo Bundle ( experimental )

This repository provides Debian-based PostGIS Docker images enriched with additional geospatial packages such as pgRouting, https://github.com/zachasme/h3-pg, https://github.com/pramsey/pgsql-ogr-fdw, MobilityDB, PL/Python3, https://pgpointcloud.github.io/pointcloud/, https://github.com/pgvector/pgvector, TimeScaleDB and others. These images serve as a comprehensive solution for various server side geospatial needs. Please note that the included package list is subject to change as we continue to refine the 'bundle0'.

⛰️Alpine 3.21 based

• The base operating system is Alpine Linux. It is designed to be small, simple, and secure, and it's based on musl libc.
• In the Alpine 3.21 version, the package versions are: geos=3.13, gdal=3.10, proj=9.5, and sfcgal=2.0
• PostGIS is compiled from source, making it a bit more challenging to extend.

⛰️Alpine 3.22 based

• The base operating system is Alpine Linux. It is designed to be small, simple, and secure, and it's based on musl libc.
• In the Alpine 3.22 version, the package versions are: geos=3.13.1, gdal=3.10.2, proj=9.6.0, and sfcgal=2.0.0
• PostGIS is compiled from source, making it a bit more challenging to extend.