I was seeing this in my app setup and was able to put together a reproducible example.
Information
OS X: version 10.11.5 (build: 15F28b)
Docker.app: version v1.11.0-beta9
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160503-091155.tar.gz
Most specific failure is: No error was detected
Your unique id is: 86DF8E94-5D0E-4814-8A71-11F007590D3D
Please quote this in all correspondence.
Steps to reproduce the behavior
Docker file
FROM postgres:latest
ENV POSTGRES_USER=csroot
ENV POSTGRES_PASSWORD=password
ENV POSTGRES_DB=csdb
ENV PGDATA=/pgdata
Create a dir with the above Dockerfile and docker-compose.yml
mkdir -p data/pgdata
docker-compose build
docker-compose up
Sorry about this next step. After doing this and running it, I was not seeing the errors. However, after I created a table in the database I created, I see them. I wasn’t able to figure out how to do this in the dockerfile so it needs to be done manually.
Since the docker containers are not run in the background, open up another terminal window:
This issue is still prevalent in the latest tag (9.5.3) and 9.6-beta1. I have run the containers in background mode and even tried without creating any data; the warning still appears.
@coltonprovias - did you edit your post? I received an email where it read that it was NOT happening with 9.6 but it now says that does still occur. Correct to assume that it did begin happening?
Thanks - that’s a great point. I had noted that “it may take a while”, but it can take around 30 minutes. I haven’t gotten any reply or acknowledgment that it’s a bug, so hopefully this will help in figuring out what’s wrong.
So far it’s just a minor annoyance, but it would still be good to get fixed eventually. I should note that I’m on Docker 0.10.3 as 0.11 doesn’t play well with Rancher.
This issue is still present on Version 1.12.0-rc3-beta18 (build: 9996) - ec40b14c72adc0bff3b01fa8886dae7f2eee1541
regarding docker’s logs this error is related to docker chmod capabilities, see lines after 2695 on the log file -starting from the end of this file will save you some scrolling time