Update postgres Docker tag to v18

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
postgres	final	major	17.7-alpine3.21 → 18.1-alpine3.21
postgres		major	17.7-alpine3.21 → 18.1-alpine3.21

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Xarlos89]

When running Postgres 18, we fail to start

✔ Image postgres:18.1-alpine3.21 Pulled                                                                                                                                                              32.4s
 ✔ Image eos-api:latest           Built                                                                                                                                                               11.7s
 ✔ Image eos-migration:latest     Built                                                                                                                                                               11.7s
 ✔ Image eos-bot:latest           Built                                                                                                                                                               11.7s
 ✔ Container db                   Recreated                                                                                                                                                            0.5s
 ✔ Container migration            Recreated                                                                                                                                                            0.4s
 ✔ Container api                  Recreated                                                                                                                                                            0.3s
 ✔ Container bot                  Recreated                                                                                                                                                            0.3s
Attaching to api, bot, db, migration
Container db Waiting 
db  | Error: in 18+, these Docker images are configured to store database data in a
db  |        format which is compatible with "pg_ctlcluster" (specifically, using
db  |        major-version-specific directory names).  This better reflects how
db  |        PostgreSQL itself works, and how upgrades are to be performed.
db  | 
db  |        See also https://github.com/docker-library/postgres/pull/1259
db  | 
db  |        Counter to that, there appears to be PostgreSQL data in:
db  |          /var/lib/postgresql
db  | 
db  |        This is usually the result of upgrading the Docker image without
db  |        upgrading the underlying database using "pg_upgrade" (which requires both
db  |        versions).
db  | 
db  |        The suggested container configuration for 18+ is to place a single mount
db  |        at /var/lib/postgresql which will then place PostgreSQL data in a
db  |        subdirectory, allowing usage of "pg_upgrade --link" without mount point
db  |        boundary issues.
db  | 
db  |        See https://github.com/docker-library/postgres/issues/37 for a (long)
db  |        discussion around this process, and suggestions for how to do so.
db exited with code 1 (restarting)                                                                                                                                                                         
db  | Error: in 18+, these Docker images are configured to store database data in a
db  |        format which is compatible with "pg_ctlcluster" (specifically, using
db  |        major-version-specific directory names).  This better reflects how
db  |        PostgreSQL itself works, and how upgrades are to be performed.
db  | 
db  |        See also https://github.com/docker-library/postgres/pull/1259
db  | 
db  |        Counter to that, there appears to be PostgreSQL data in:
db  |          /var/lib/postgresql
db  | 
db  |        This is usually the result of upgrading the Docker image without
db  |        upgrading the underlying database using "pg_upgrade" (which requires both
db  |        versions).
db  | 
db  |        The suggested container configuration for 18+ is to place a single mount
db  |        at /var/lib/postgresql which will then place PostgreSQL data in a
db  |        subdirectory, allowing usage of "pg_upgrade --link" without mount point
db  |        boundary issues.
db  | 
db  |        See https://github.com/docker-library/postgres/issues/37 for a (long)
db  |        discussion around this process, and suggestions for how to do so.
db exited with code 1 (restarting)                                                                                                                                                                         
db  | Error: in 18+, these Docker images are configured to store database data in a
db  |        format which is compatible with "pg_ctlcluster" (specifically, using
db  |        major-version-specific directory names).  This better reflects how
db  |        PostgreSQL itself works, and how upgrades are to be performed.
db  | 
db  |        See also https://github.com/docker-library/postgres/pull/1259
db  | 
db  |        Counter to that, there appears to be PostgreSQL data in:
db  |          /var/lib/postgresql
db  | 
db  |        This is usually the result of upgrading the Docker image without
db  |        upgrading the underlying database using "pg_upgrade" (which requires both
db  |        versions).
db  | 
db  |        The suggested container configuration for 18+ is to place a single mount
db  |        at /var/lib/postgresql which will then place PostgreSQL data in a
db  |        subdirectory, allowing usage of "pg_upgrade --link" without mount point
db  |        boundary issues.
db  | 
db  |        See https://github.com/docker-library/postgres/issues/37 for a (long)
db  |        discussion around this process, and suggestions for how to do so.

Container db Error dependency postgres failed to start
dependency failed to start: container db is unhealthy

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 18.x releases. But if you manually upgrade to 18.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.