I have a docker compose setup that was working before (for several months) but after restarting the Pi its now not working :(

Whats to be noted is that when pointing the DB to an empty DB folder, there are no restarts of the Postgres container and no errors. I tried one backup from the past for the DB data folder but still getting the error. Not sure why?

Here is the error postgres is returning:

```
PostgreSQL Database directory appears to contain a database; Skipping initialization

2021-03-30 13:38:46.052 UTC [1] LOG:  starting PostgreSQL 12.1 (Debian 12.1-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
2021-03-30 13:38:46.053 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2021-03-30 13:38:46.053 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2021-03-30 13:38:46.063 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-03-30 13:38:48.195 UTC [1] LOG:  startup process (PID 26) was terminated by signal 11: Segmentation fault
2021-03-30 13:38:48.195 UTC [1] LOG:  aborting startup due to startup process failure
2021-03-30 13:38:48.272 UTC [1] LOG:  database system is shut down

```

Here is part of the docker compose file for the DB:

```
  miniflux-db:
    container_name: miniflux-db
    image: postgres:12-alpine
    environment:
      - POSTGRES_USER=${MINIFLUX_DB_USER}
      - POSTGRES_PASSWORD=${MINIFLUX_DB_PASSWORD}
    restart: unless-stopped
    volumes:
      - ${MINIFLUX_DB}:/var/lib/postgresql/data:shared
    networks:
      - miniflux-net

```

Info:
Raspberry Pi 4
Docker version 20.10.5, build 55c4c88

I can't even port the data to version 13 of Postgres nor use the Postgres DB folder on an Intel architecture. Had I known that Postgres DB data folder is architecture-bound I would not have chosen it!

Any help pls? Thanks!