Production branch builds are broken due to postgres no longer serving buster repository

[ChrisW-B]

Describe the bug
When trying to start up bookwyrm on a self hosted server, you can no longer do so as postgres's apt repository no longer includes buster

To Reproduce
Steps to reproduce the behavior:

1. Clear your docker builds
2. Run ./bw-dev up
3. See error

Expected behavior
bookwyrm should build normally

Screenshots
apt reports first
404 Not Found [IP: 147.75.85.69 80]
and then fails with
E: The repository 'http://apt.postgresql.org/pub/repos/apt buster-pgdg Release' does not have a Release file.

Instance
Selfhosted, latest commit on production branch

[qisantanu]

Let us know if any solution acheived.
I am facing this:

[ChrisW-B]

As a temp fix, you can update postgres-docker/Dockerfile in two places:

on line 1,

- FROM postgres:13.0 
+ FROM postgres:13.16

and on line 18

- RUN awk '$0 ~ /^\t_main "\$@"$/ { print "\tif [[ $1 == cron ]]; then\n\t\techo \"POSTGRES_DB=${POSTGRES_DB}\" > /backups/.env\n\t\techo \"POSTGRES_USER=${POSTGRES_USER}\" >> /backups/.env\n\t\tservice cron start\n\t\tshift\n\tfi" }{ print }' docker-entrypoint.sh > bookwyrm-entrypoint.sh
+ RUN awk '$0 ~ /^\t_main "\$@"$/ { print "\tif [[ $1 == cron ]]; then\n\t\techo \"POSTGRES_DB=${POSTGRES_DB}\" > /backups/.env\n\t\techo \"POSTGRES_USER=${POSTGRES_USER}\" >> /backups/.env\n\t\tservice cron start\n\t\tshift\n\tfi" }{ print }' /usr/local/bin/docker-entrypoint.sh > bookwyrm-entrypoint.sh

postgres moved the place of their entrypoint file, so you can't just update postgres. I'm not sure if the package maintainers want a specific version of postgres, so I'm hesitant to add a PR

[CypherJack]

I face the same issue I will try your temp fix thanks !

[qisantanu]

I started using:

RUN curl -sSL https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add - \ && echo 'deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main' $PG_MAJOR > /etc/apt/sources.list.d/pgdg.list

[OliverPifferi]

As a temp fix, you can update postgres-docker/Dockerfile in two places:

Thanks for this hint - this helped me a lot when moving to my new instance and wondering why the setup crashed. Made my day! ♥️