moby: Postgres data volume is mounted with wrong permissions in Docker OSX beta

The directory /var/lib/postgresql/data doesn’t exist in the VM because only certain host first-level directories are available: right now, /Users, /Volumes, /tmp, and /private. See Namespaces on https://beta.docker.com/docs/mac/osxfs/ for the full details. We’re currently considering changing the bind mount namespace behavior but this is how it works currently. Solutions for right now are either:

1. Prepending /Mac to the path
2. Using a path under one of the above first-level directories

Finally, you may run into further issues running postgres on a shared bind mount as we don’t currently support fallocate or [f]stat[v]fs but will in a Beta Coming Soon.

Update!

volumes:
          - /tmp:/tmp_host
          - /Users/ilya/postgresql-data2/:/var/lib/postgresql/data

• /data Works!

When I ran that (on Docker for Mac), it ran without issues;

postgres_1  | The files belonging to this database system will be owned by user "postgres".
postgres_1  | This user must also own the server process.
postgres_1  |
postgres_1  | The database cluster will be initialized with locale "en_US.utf8".
postgres_1  | The default database encoding has accordingly been set to "UTF8".
postgres_1  | The default text search configuration will be set to "english".
postgres_1  |
postgres_1  | Data page checksums are disabled.
postgres_1  |
postgres_1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok

....

this database system will be owned by user "postgres"

But, I have this problem.Why?Could you help me?

@shabbirkagalwala Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting bugs and feature requests. For other type of questions, consider using one of;

• https://forums.docker.com
• the Docker community Slack channel
• StackOverflow

@esbenp @duykhoa is this still an issue for you on the latest Docker for Mac beta?

Just ran this;

mkdir postgres && cd postgres
docker run --rm -v `pwd`:/var/lib/postgresql/data -p 5432:5432 postgres
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
....
....
LOG:  database system is ready to accept connections

@dsheets in this case, it’s not a bind-mounted directory, so - /var/lib/postgresql/data should create a new, “anonymous” volume.

@esbenp is there a reason you’re using a data-only container? docker now has volume management functions (docker volume ls, docker volume create). In this case, I suggest to use a named volume for your postgres data, e.g.

postgres:
  image: traede/postgres:0.1
  ports:
    - "5432:5432"
  volumes:
    - postgres_data:/var/lib/postgresql/data

You can find that volume with docker volume ls;

docker volume ls                                                                                                                                               DRIVER              VOLUME NAME
local               postgres_data

thanks @samoht!

closing this issue, but feel free to comment here if you still run into this issue

@duykhoa oh, just got notified that there’s still an issue when bind-mounting a local directory for postgresql; https://forums.docker.com/t/beta-9-postgres-stat-files-corrupted-when-data-stored-on-host-mapped-volume/10819

So, yes (also for performance), using a volume instead of a bind-mounted host-directory is still the preferred approach

Oh, perhaps docker-compose down first to be sure the old containers and volumes of the project are removed (assuming there’s no important data in there)