Add new base distro: Ubuntu

[MattFromGer]

Does anybody want to invest time adding Ubuntu as a new distro base besides Debian and Alpine?

Background: Timescale HA is using Ubuntu as base distro and after some hours of fiddeling I'm stuck at pg_upgrade with an SSL error. Maybe this is caused by the base distro mismatch?

FROM timescale/timescaledb-ha:pg14.17-ts2.19.0 AS pg14
FROM pgautoupgrade/pgautoupgrade:17.7-debian

COPY --from=pg14 /usr/lib/postgresql/14/lib /usr/local-pg14/lib/postgresql
COPY --from=pg14 /usr/share/postgresql/14 /usr/local-pg14/share/postgresql

pg-autoupgrade-local-1 | Running pg_upgrade command, from /var/lib/postgresql/data
pg-autoupgrade-local-1 | ---------------------------------------
pg-autoupgrade-local-1 | Performing Consistency Checks
pg-autoupgrade-local-1 | -----------------------------
pg-autoupgrade-local-1 | Checking cluster versions ok
pg-autoupgrade-local-1 | SQL command failed
pg-autoupgrade-local-1 | SELECT pg_catalog.set_config('search_path', '', false);
pg-autoupgrade-local-1 | ERROR: could not load library "/usr/local-pg14/lib/postgresql/timescaledb-2.19.0.so": /usr/local-pg14/lib/postgresql/timescaledb-2.19.0.so: undefined symbol: SSL_get_error

[andyundso]

Hi @MattFromGer

Sorry that you never received an answer here. maybe you already found a solution, otherwise my two cents below.

I looked up the repository at the time and indeed, Timescale builds from Ubuntu. Actually they still do today :)

Ubuntu 22.04 uses OpenSSL v3.0.2, our current Debian image, based on Trixie, should use v3.5. API / ABI should be compatible between these versions. I guess the problem is actually the Postgres binaries that pgautoupgrade provides that are compiled without SSL support.

Given the many extensions that are baked into this timescale image, I am wondering if it wouldn't be better to do a pg_dumpall on your current instance and then import it into new instance of this Timescale image. I feel bad for advertising against our own product, but I looked at the Dockerfile of this Timescale image and when I see Rust, SSL, PostGIS, AI stuff, PG Vector ... I don't know, it just seems not ideal for a pg_upgrade.

[MattFromGer]

No worries @andyundso
You're indeed correct with your observations!
I found out that Timescale provides containers with the tag -all at the end, which contain binaries for at least 3 postgres major versions. I guess they were created for the sole purpose of majors upgrades. So I used that one and wrote my own update script which worked flawlessly.

[andyundso]

perfect, thanks for the update!