-
-
Notifications
You must be signed in to change notification settings - Fork 107
Closed
Description
I got this error while trying to create an instance using postgres:18.0-trixie, released some days ago:
turicas@xxx:/storage$ dokku postgres:create "$NEW_PG_NAME" -i postgres -I "18.0-trixie"
18.0-trixie: Pulling from library/postgres
8c7716127147: Pull complete
1014e14b3351: Pull complete
edd90ab5059f: Pull complete
f0d70120d9e2: Pull complete
dd6d7b9d8ba8: Pull complete
203b16f56a7d: Pull complete
751039babae5: Pull complete
f5af7533693a: Pull complete
9a68d6020eab: Pull complete
f69a7c424b50: Pull complete
eed0ac863490: Pull complete
2433c366ca00: Pull complete
a585c5f82f15: Pull complete
af60ce4418c9: Pull complete
Digest: sha256:ad98a3ba6a3b5e53e9bd95afed6930d3103efc890240643a168b590bcf2e6e81
Status: Downloaded newer image for postgres:18.0-trixie
docker.io/library/postgres:18.0-trixie
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/dokku/services/postgres/pg18_criobot/data" to rootfs at "/var/lib/postgresql/data": change mount propagation through procfd: open o_path procfd: open /var/lib/docker/overlay2/430efdf52cabf75a008b057e58a9e7580b2464edaf4364fe1dc6fc6581a4b4c7/merged/var/lib/postgresql/data: no such file or directory: unknown
Error: failed to start containers: 0ad458efb39b695155ccdc05ee4550e1cbb23499fd5bd880addefef3bbd00a2d
From https://henrywithu.com/upgrade-postgresql-from-17-to-18-on-docker/:
A key change to be aware of is that starting with version 18, the official PostgreSQL Docker image uses a version-specific data directory path (
/var/lib/postgresql/18/datainstead of the generic/var/lib/postgresql/data).
Related issue: geekau/mediastack#55
Metadata
Metadata
Assignees
Labels
No labels