-
Notifications
You must be signed in to change notification settings - Fork 225
Conversation
Hi guys! I believe that you approve this commit! |
Hey, can we merge this? |
Also eagerly awaiting this :) @eeshugerman any chance this Pr could get merged and the image published? 🚀 |
Thanks @ledermann for the PR! Has anyone tested this out? Best I can tell Postgres v16 is not available in Alpine v3.18. |
@eeshugerman Yes, it seems this PR is a bit premature - support for PostgreSQL 16 has not landed in Alpine 3.18: $ docker run -it --rm alpine /bin/sh
/ # apk update
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/aarch64/APKINDEX.tar.gz
v3.18.4-82-gbad06ca2153 [https://dl-cdn.alpinelinux.org/alpine/v3.18/main]
v3.18.4-80-g1df2bca78e9 [https://dl-cdn.alpinelinux.org/alpine/v3.18/community]
OK: 19946 distinct packages available
/ # apk add postgresql-client
(1/8) Installing postgresql-common (1.2-r0)
Executing postgresql-common-1.2-r0.pre-install
(2/8) Installing lz4-libs (1.9.4-r4)
(3/8) Installing libpq (15.4-r0)
(4/8) Installing ncurses-terminfo-base (6.4_p20230506-r0)
(5/8) Installing libncursesw (6.4_p20230506-r0)
(6/8) Installing readline (8.2.1-r1)
(7/8) Installing zstd-libs (1.5.5-r4)
(8/8) Installing postgresql15-client (15.4-r0)
Executing busybox-1.36.1-r2.trigger
Executing postgresql-common-1.2-r0.trigger
* Setting postgresql15 as the default version
OK: 13 MiB in 23 packages
/ # apk add postgresql16-client
ERROR: unable to select packages:
postgresql16-client (no such package):
required by: world[postgresql16-client] Currently, I guess we'll have to wait a little longer. |
This requires Alpine 3.19
In the meantime, Alpine 3.19 has been released with support for PostgreSQL 16, so this PR should be ready to merge. |
Any volunteers to test this? |
@eeshugerman I can try if that would help. I can try if a test version is tagged. I make a daily backup on a database on my docker compose and since v16 it has been stopped. |
Thanks @Ardakilic; I found some free time so went ahead and tested myself. There is a minor snag:
We can address this by switching from |
Since Postgres 11 users can still use the old tag, and v11 is EOL already, I'd personally go for it. |
Hey folks, can we merge this =) ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build fails -- see #39 (comment)
I believe this line should be removed: And these two lines should be modified as @eeshugerman mentioned: @ledermann could you check please? |
Version 11 has reached end-of-life (EOL) https://www.postgresql.org/support/versioning/
This removes python3 and py3-pip as explicit dependencies. Python is still installed as a derived dependency. This fixes building on Alpine 3.19
Sorry, folks, for not testing my own PR. I have made the changes as requested. Now, the Docker image builds fine for Alpine from |
Looks good, thanks @ledermann! |
* Add support for PostgreSQL 16 This requires Alpine 3.19 * Drop support for PostgreSQL 11 Version 11 has reached end-of-life (EOL) https://www.postgresql.org/support/versioning/ * Install aws-cli via apk instead of pip3 This removes python3 and py3-pip as explicit dependencies. Python is still installed as a derived dependency. This fixes building on Alpine 3.19
PostgreSQL 16 was released on 2023-09-14:
https://www.postgresql.org/about/news/postgresql-16-released-2715/
PostgreSQL 11 has reached end-of-life by 2023-11-09:
https://www.postgresql.org/support/versioning/
This PR enhances the build matrix (adding v16, removing v11), simplifies installing
aws-cli
(by usingapk
) and updates the README.