Migrated to Docker weeks ago, now suddenly docker image is not starting due PSQL

I moved from old classic install to a docker image already 5-6 weeks ago.
All fine, just today the firezone was unreachable, I checked the host and saw docker is down.
I did a docker compose up and now I got flooded with postgress error.

firezone-postgres-1  |
firezone-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
firezone-postgres-1  |
firezone-postgres-1  | 2023-03-20 10:51:01.784 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
firezone-postgres-1  | 2023-03-20 10:51:01.785 UTC [1] LOG:  listening on IPv4 address "", port 5432
firezone-postgres-1  | 2023-03-20 10:51:01.785 UTC [1] LOG:  listening on IPv6 address "::", port 5432
firezone-postgres-1  | 2023-03-20 10:51:01.786 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
firezone-postgres-1  | 2023-03-20 10:51:01.789 UTC [27] LOG:  database system was shut down at 2023-03-20 10:39:29 UTC
firezone-postgres-1  | 2023-03-20 10:51:01.791 UTC [1] LOG:  database system is ready to accept connections
firezone-firezone-1  | Creating WireGuard interface wg-firezone
firezone-firezone-1  | Adding route for interface wg-firezone
firezone-firezone-1  | Adding route fd00::3:2:0/120 for interface wg-firezone
firezone-firezone-1  | 10:51:05.281 erl_level=error application=ecto_sql domain=elixir file=lib/ecto/migrator.ex function=verbose_schema_migration/3 line=680 mfa=Ecto.Migrator.verbose_schema_migration/3 module=Ecto.Migrator pid=<0.95.0> [error] Could not create schema migrations table. This error usually happens due to the following:
firezone-firezone-1  |
firezone-firezone-1  |   * The database does not exist
firezone-firezone-1  |   * The "schema_migrations" table, which Ecto uses for managing
firezone-firezone-1  |     migrations, was defined by another library
firezone-firezone-1  |   * There is a deadlock while migrating (such as using concurrent
firezone-firezone-1  |     indexes with a migration_lock)
firezone-firezone-1  |
firezone-firezone-1  | To fix the first issue, run "mix ecto.create".
firezone-firezone-1  |
firezone-firezone-1  | To address the second, you can run "mix ecto.drop" followed by
firezone-firezone-1  | "mix ecto.create". Alternatively you may configure Ecto to use
firezone-firezone-1  | another table and/or repository for managing migrations:
firezone-firezone-1  |
firezone-firezone-1  |     config :fz_http, FzHttp.Repo,
firezone-firezone-1  |       migration_source: "some_other_table_for_schema_migrations",
firezone-firezone-1  |       migration_repo: AnotherRepoForSchemaMigrations
firezone-firezone-1  |
firezone-firezone-1  | The full error report is shown below.
firezone-firezone-1  |
firezone-firezone-1  | ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2991ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
firezone-firezone-1  |
firezone-firezone-1  |   1. Ensuring your database is available and that you can connect to it
firezone-firezone-1  |   2. Tracking down slow queries and making sure they are running fast enough
firezone-firezone-1  |   3. Increasing the pool_size (although this increases resource consumption)
firezone-firezone-1  |   4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
firezone-firezone-1  |
firezone-firezone-1  | See DBConnection.start_link/2 for more information
firezone-firezone-1  |
firezone-firezone-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
firezone-firezone-1  |     (elixir 1.14.3) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
firezone-firezone-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:1005: Ecto.Adapters.SQL.execute_ddl/4
firezone-firezone-1  |     (ecto_sql 3.9.2) lib/ecto/migrator.ex:677: Ecto.Migrator.verbose_schema_migration/3
firezone-firezone-1  |     (ecto_sql 3.9.2) lib/ecto/migrator.ex:491: Ecto.Migrator.lock_for_migrations/4
firezone-firezone-1  |     (ecto_sql 3.9.2) lib/ecto/migrator.ex:403: Ecto.Migrator.run/4
firezone-firezone-1  |     (ecto_sql 3.9.2) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3
firezone-firezone-1  |     nofile:1: (file)
firezone-firezone-1 exited with code 1

Thats weird and I cant seems get it to run anymore.

Anybody have a suggestion?

Is there anything suspicious in the logs for Postgres container? Also, is it running? (docker ps will tell you)