ImreSamu

Results 138 comments of ImreSamu

@akorotkov : > Merged in f282011. I believe the f282011 commit is from a previous PR made a year ago, committed on June 11, 2023. This PR is an update...

Hi @latot , Currently, this program runs on initialization : https://github.com/postgis/docker-postgis/blob/master/15-3.3/initdb-postgis.sh And there are historical reasons for this, some want more extensions, some want less, some want configurable (https://github.com/postgis/docker-postgis/issues/187 )...

> I'm developing an open-source action that utilizes Dive .... > ... Could you please let me know your requirements > so I can consider them while building it? Thanks!...

Hi @jvacek ! > The official postgres has support for passing the env var POSTGRES_INITDB_ARGS, > which would be a lot less hacky than this and would allow me to...

Hi @harmv Thank you for sending this question! The large image size is a valid concern, but I don't know how to significantly reduce the size even more. ( Sure...

Hi @harmv, I think I found the reason for the increase in the alpine image size. [in the build log](https://pipelines.actions.githubusercontent.com/serviceHosts/86ac2020-4c5f-4310-a2ae-0f49a53e6a3b/_apis/pipelines/1/runs/386/signedlogcontent/12?urlExpires=2023-02-04T19%3A00%3A39.0848337Z&urlSigningMethod=HMACV1&urlSignature=%2B0Kcxt4czU3E5qD6EMl%2Bmo5dsartuAI1YSxwZOaC%2BQ8%3D) : `2023-01-30T05:23:59.3772866Z (84/136) Upgrading llvm15-libs (15.0.6-r0 -> 15.0.7-r0)` And now...

> [edit] It seems LLVM is required for JIT. Which is debatable wether you need that in the alpine image. imho: "Breaking change" is not good for existing users, so...

@harmv : Now the latest **`postgis/postgis:13-3.3-alpineΛ™ is 425MB** and your proposal is 475MB, And both dockerfiles are quite complex, so suddenly I don't know why there is such a big...

> I am a bit surprised about the versioning in docker images though.... > postgres :13-alpine3.17 of two weeks ago it not the same as postgres:13-alpine3.17 of now. > postgis:13-3.3-alpine...

Thank you for the issue! It does seem like something is missing. However, since we also use the Debian PostGIS package, specifically * `postgresql-15-postgis-3` and `postgresql-15-postgis-3-scripts`, * https://github.com/postgis/docker-postgis/blob/master/15-3.4/Dockerfile * `postgresql-16-postgis-3`...