(Mac+VFS) data directory "/var/lib/postgresql/data" has wrong ownership

[daweimau]

Given the below docker-compose yml:

version: "3.7"

services:
    db:
        container_name: db
        image: postgis/postgis:15-3.4-alpine
        ports:
            - "5010:5432"  
        environment:
            POSTGRES_DB: my-db
            POSTGRES_USER: postgres
            POSTGRES_PASSWORD: verysecretpass
        volumes:
            - ./pgdata:/var/lib/postgresql/data 

• If we replace image with postgres:alpine, we have no issues. Everything works.
• If we use postgis/postgis:15-3.4-alpine, building the image seems ok, and first run also seems ok. Subsequent runs with docker compose up db will produce this error:

db  | 2023-09-17 01:22:45.415 UTC [1] FATAL:  data directory "/var/lib/postgresql/data" has wrong ownership
db  | 2023-09-17 01:22:45.415 UTC [1] HINT:  The server must be started by the user that owns the data directory.

But it works with the postgres alpine image. Why should it not work now?

Seeing as we extend the postgres-alpine image, and postgres-alpine works, I figured we must be introducing the problem after the base image layers / entrypoint.

• Copied down the postgis alpine Dockerfile and sh scripts, and adjusted docker-compose.yml to build from a local image instead:

    db:
        container_name: db
        build:
            context: "./pg"
            dockerfile: "./Dockerfile"
        ports:

• Then ran into Error command not found in initdb-postgis.sh #360
• However, noticed even with this separate issue, I could still repro the error I cared about: data directory "/var/lib/postgresql/data" has wrong ownership
• For completeness, decided to try getting around Error command not found in initdb-postgis.sh #360 before resuming this issue
• Implemented my workaround for Error command not found in initdb-postgis.sh #360 as described here

Since doing so, the data directory "/var/lib/postgresql/data" has wrong ownership error has disappeared.

I don't understand the details. But I believe the initdb-postgis.sh script is doing it

[ImreSamu]

Thank you for reporting this issue!

To better assist you, could you provide more details about:

• Your operating system and its version
• The Docker / docker-compose version you are using
• Any other relevant information that might help prevent similar issues in the future would also be appreciated.

By the way, what exact filesystem do you have under the volume? ( ./pgdata: )

For instance, postgres doesn't work for others under Mac/VirtioFS either.

• virtiofs breaks initial startup of Postgres container docker/for-mac#6270

Please try using "docker volume" as a workaround. It has solved the problem for many.

• virtiofs breaks initial startup of Postgres container docker/for-mac#6270 (comment)

Please also check the related issues in the

• https://github.com/search?q=repo%3Adocker-library%2Fpostgres+data+directory+%22%2Fvar%2Flib%2Fpostgresql%2Fdata%22+has+wrong+ownership&type=issues

If we replace image with postgres:alpine, we have no issues. Everything works.

Please also replace the data dir ( ./pgdatapostgres01: vs. ./pgdatapostgis02: ) and check the logs for the initialization process.
Please share both logs so we can check.

I don't understand the details. But I believe the initdb-postgis.sh script is doing it

There are two initialization steps, which can be challenging to debug. Please share your initialization logs with us.

Or you can replace/remove the postgis initialization with a dummy script, so the original 10_postgis.sh is not running.

• -v $(pwd)/10_postgis.sh:/docker-entrypoint-initdb.d/10_postgis.sh

[daweimau]

os

Mac M1 pro sillicon
macOS Ventura 13.5.1
Docker 4.11.0 

Thanks for your links. Reading them made me more suspicious of my workaround. I've since confirmed:

• My workaround in OP does not reliably work - only intermittently. That aligns with some other users experience of the root issue
• Based on other posts and your advice, I confirmed below in my case:
  • Docker 4.11 + VFS enabled - Never works (other than first run)
  • Docker 4.11 + VFS disabled - Seems to always work, could not reproduce issue
  • Docker 4.23 + VFS enabled - Seems to always work, could not reproduce issue
  • Docker 4.23 + VFS disabled (use gRPC) - Seems to always work, could not reproduce issue

The behaviour can be quite intermittent so I will come back if my observation changes; I will continue with 4.23+VFS

[ImreSamu]

The behaviour can be quite intermittent so I will come back if my observation changes; I will continue with 4.23+VFS

I am closing this issue.
However, if there is any important matter that was overlooked, please let me know and I will reopen the issue.