Just a heads up – having a front page catastrophic error in my Lemmy containers:

dessalines/lemmy-ui    latest       5c9f05cd560a   39 hours ago   541MB
dessalines/lemmy       latest       7e2eba20fe06   2 days ago     184MB

I am logging the following error on a root page load:

API error: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo ENOTFOUND lemmy

CONTAINER ID   IMAGE                      COMMAND                  CREATED          STATUS                          PORTS                                           NAMES
bb9796b61988   nginx:1-alpine             "/docker-entrypoint.…"   13 minutes ago   Up 13 minutes                   80/tcp, 0.0.0.0:80->8536/tcp, :::80->8536/tcp   lemmy-proxy-1
bf01a6e036ad   dessalines/lemmy-ui        "docker-entrypoint.s…"   13 minutes ago   Up 13 minutes                   1234/tcp                                        lemmy-lemmy-ui-1
048d83dfa060   dessalines/lemmy           "/app/lemmy"             13 minutes ago   Restarting (1) 34 seconds ago                                                   lemmy-lemmy-1
1bd0b69dc05d   mwader/postfix-relay       "/root/run"              13 minutes ago   Up 13 minutes                   25/tcp                                          lemmy-postfix-1
d6570da3a505   asonix/pictrs:0.4.0-rc.7   "/sbin/tini -- /usr/…"   13 minutes ago   Restarting (1) 35 seconds ago                                                   lemmy-pictrs-1
84d376fa813a   postgres:15-alpine         "docker-entrypoint.s…"   13 minutes ago   Up 13 minutes                   5432/tcp                                        lemmy-postgres-1

I see the lemmy container unable to start. Restarting the docker containers in non-daemon mode I get the following logged, which explains why the lemmy container is crashing:

lemmy-postfix-1   | 2023-09-29T11:18:15.825112+00:00 1bd0b69dc05d postfix/master[149]: daemon started -- version 3.4.23, configuration /etc/postfix
lemmy-postgres-1  | 2023-09-29 11:18:15.856 UTC [32] ERROR:  column person.admin does not exist at character 394
lemmy-postgres-1  | 2023-09-29 11:18:15.856 UTC [32] STATEMENT:  SELECT "person"."id", "person"."name", "person"."display_name", "person"."avatar", "person"."banned", "person"."published", "person"."updated", "person"."actor_id", "person"."bio", "person"."local", "person"."private_key", "person"."public_key", "person"."last_refreshed_at", "person"."banner", "person"."deleted", "person"."inbox_url", "person"."shared_inbox_url", "person"."matrix_user_id", "person"."admin", "person"."bot_account", "person"."ban_expires", "person"."instance_id" FROM "person" WHERE (("person"."actor_id" LIKE $1) AND ("person"."local" = $2))
lemmy-lemmy-1     | Error: 
lemmy-lemmy-1     | LemmyError
lemmy-lemmy-1     |  { 
lemmy-lemmy-1     | message
lemmy-lemmy-1     | : 
lemmy-lemmy-1     | None
lemmy-lemmy-1     | , 
lemmy-lemmy-1     | inner
lemmy-lemmy-1     | : 
lemmy-lemmy-1     | column person.admin does not exist, context: SpanTrace 
lemmy-lemmy-1     | [
lemmy-lemmy-1     | ]
lemmy-lemmy-1     |  }
lemmy-lemmy-1     | 
lemmy-lemmy-1     | 
lemmy-pictrs-1 exited with code 1
lemmy-lemmy-1 exited with code 1

Just a heads up – not a bug report.