Re: Docker images from Jan 22 forward failing to start on raspberry pi 4

Hello Dmitry,

I was about to follow the guide you posted but in the process of deploying
the image, I noticed that 13.2 was released 11 hours ago
<https://hub.docker.com/layers/postgres/library/postgres/13.2/images/sha256-ef7278c4fb90d44bc6495114ca65a01bcaca0b43e6671283e157d3f642facd94?context=explore>.
This release has solved the issue. Was the problem already found and fixed?
If not would it still be useful to provide a stack trace running 13.1?

Regards,
Will

On Tue, 9 Feb 2021 at 14:12, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:

> > On Tue, Feb 09, 2021 at 09:53:23AM +1000, William Hingston wrote:
> >
> > The dockers images after Jan 22 fail to start on arm64 (tested on my
> > raspberry pi 4).
> >
> >
> https://stackoverflow.com/questions/65877033/postgressql-terminates-with-signal-11-when-run-with-docker-compose
> >
> https://stackoverflow.com/questions/65938577/why-is-my-postgres-database-working-for-a-while-and-then-not-able-to-start-serv
> >
> > db_1 | Success. You can now start the database server using:
> > db_1 |
> > db_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
> > db_1 |
> > db_1 | waiting for server to start....[36] LOG: starting PostgreSQL
> > 13.1 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine
> > 10.2.1_pre1) 10.2.1 20201203, 32-bit
> > db_1 | [36] LOG: listening on Unix socket
> "/var/run/postgresql/.s.PGSQL.5432"
> > db_1 | ......[36] LOG: startup process (PID 37) was terminated by
> > signal 11: Segmentation fault
> > db_1 | [36] LOG: aborting startup due to startup process failure
> > db_1 | [36] LOG: database system is shut down
> > db_1 | pg_ctl: could not start server
> > db_1 | Examine the log output.
> > db_1 | stopped waiting
>
> Interesting. There are build farm members with arm64 architechture, and
> they're not complaining as far as I see, but they're also not compiled
> with musl. Can you maybe provide a core dump or at least a stack trace?
>
> [1]:
> https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>