update Docker container offerings

[tomkralidis]

Currently, pygeoapi produces Docker images via GitHub Actions to the following container registries:

• Docker Hub (on release, and latest based on master branch)
• GitHub Container Registry (latest based on master branch)

Currently, the latest image is ~1.5GB containing numerous optional dependencies. It would be valuable to offer various images based on different deployment profiles/environments.

• [ ] determine images to produce (e.g. slim, default, full)
• [ ] add/update Dockerfile setups accordingly
• [ ] update GitHub Action for container publication
• [ ] update documentation

cc @justb4 @francbartoli @webb-ben @ricardogsilva

[github-actions[bot]]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.

[kalxas]

I have been experimenting with a slim version of our Docker image. I agree it would be good to have different images for different use cases.

[mattdear]

I have started using Pygeoapi recently and I am interested in trying to reduce the image size and resource requirements for cheaper cloud deployments and improved security.

I was thinking about trying to build the pygeoapi image with the Ubuntu/python base. https://hub.docker.com/r/ubuntu/python

@kalxas can I ask what base images you have tried? And how successful you have been?

[mikebelanger]

I'd be interested in what you've found too @kalxas.

[cmotadev]

Hey guys, I’ve already did it with Debian Bookworm and python. With some deep modifications. I’m testing some stuff but the results are promising

Greetings

Carlos Eduardo Mota

Em ter., 15 de abr. de 2025 às 13:24, Mike @.***> escreveu:

I'd be interested in what you've found too @kalxas https://github.com/kalxas.

— Reply to this email directly, view it on GitHub https://github.com/geopython/pygeoapi/issues/1753#issuecomment-2806742635, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABA76NJADWELMCZV6RTYOB32ZUXFPAVCNFSM6AAAAABLMGRHDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBWG42DENRTGU . You are receiving this because you are subscribed to this thread.Message ID: @.***> mikebelanger left a comment (geopython/pygeoapi#1753) https://github.com/geopython/pygeoapi/issues/1753#issuecomment-2806742635

I'd be interested in what you've found too @kalxas https://github.com/kalxas.

— Reply to this email directly, view it on GitHub https://github.com/geopython/pygeoapi/issues/1753#issuecomment-2806742635, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABA76NJADWELMCZV6RTYOB32ZUXFPAVCNFSM6AAAAABLMGRHDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBWG42DENRTGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[cmotadev]

Hey guys, I’ve already did it with Debian Bookworm and python. With some deep modifications. I’m testing some stuff but the results are promising

Greetings

Carlos Eduardo Mota

Em ter., 15 de abr. de 2025 às 13:24, Mike @.***> escreveu: …

@tomkralidis @kalxas @mikebelanger

PyGeoAPI`s debian based image, multi-staged, rootless and virtualenv-based, with fixed versions (experimental)

https://github.com/nds-cprm/pygeoapi.git

[github-actions[bot]]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.

[github-actions[bot]]

As per RFC4, this Issue has been closed due to there being no activity for more than 90 days.

[github-actions[bot]]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.