New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres failing to start #1
Comments
This is a well discussed issue around docker/aufs containers where confusion on how aufs treats files modified in different layers appear on permissions. For other lateral/example discussions, see: |
Since it is a problem touching file permissions, one can try to manual fix the problem, like in this comment. Or something like that, people have been discussing. The better solution, though, is to use DeviceMapper as the fs driver, instead of AUFS. At least that is what people there (at docker and surroundings) are proposing. So, to change your storage driver, add the option |
Just keep it open as a source of info before I put it clear in ("known issue") documentation. (when there is a documentation actually :-P) |
I tried to use '--no-cache' when building the image (like suggested by this comment) and it looks like it worked. |
PostgreSQL may fail at startup with /etc/ssl/private/ssl-cert-snakeoil.key permission denied. This is due to a limitation of the AUFS backend which can be worked around by recreating the /etc/ssl/private directory. Ref to gavodachs/docker-dachs#1 for the actual bug and moby/moby#783 for more details on the AUFS issue. Change-Id: I0afe01e880f4ace4a38d3751a8c621c97d97d658
Reorder layer commands in order to install ssl-cert in the first layer in order to avoid permission denied issue when starting postgresql on /etc/ssl/private/ssl-cert-snakeoil.key. This is due to a limitation of the AUFS docker backend. Ref to gavodachs/docker-dachs#1 for an instance of the bug and to moby/moby#783 for more details on the AUFS issue. Change-Id: I0afe01e880f4ace4a38d3751a8c621c97d97d658
Trying to start, postgres raises the following message
Of course, the server does not start and everything else fails.
The text was updated successfully, but these errors were encountered: