-
Notifications
You must be signed in to change notification settings - Fork 57
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
Permission denied on SSL certificat #30
Comments
+1 |
It has something to do with phusion/baseimage. I reverted it to phusion/baseimage:0.9.10 and it worked. |
Ok, found a solution. Build a new image with --no-cache option from Dockerfile. And probably the image needs to be rebuilt? @Painted-Fox ? Seems like it's a bug with AuFS mentioned by jpetazzo, not sure if it's relevant though. |
@alejo90 yes, it's the phusion/baseimage. I moved to |
Im still seeing this issue using the current build from the docker registry.
|
+1. I'm seeing this error too. Postgres is starting up when the image is built with the |
+1 |
+1
Here's the original Docker/AuFS bug moby/moby#783 Any workaround? |
I also encountered this issue, and the work-around is to use devicemapper instead of AUFS. Add this line in /etc/default/docker: DOCKER_OPTS="--storage-driver=devicemapper" and restart the docker service. |
Well, there seems to be problem with devicemapper too, as mentioned in moby/moby#4860. So, it seems, that it would be better to rebuild the image, as mentioned by @Erowlin |
I tried using devicemapper as a backend and started running into this issue: Still have the original AUFS problem w/o the dm backend |
I've created pull request based on @Erowlin's comment at #38 It works fine. |
it would be nice to have an updated version pushed to the registry |
+1 |
Running into this issue as well. |
Fresh install,
docker pull paintedfox/postgresql
andHere is the log :
POSTGRES_USER=super
POSTGRES_PASS=xxx
POSTGRES_DATA_DIR=/data
POSTGRES_DB=database_name
Starting PostgreSQL...
Couldn't initialize inotify. Are you running Linux 2.6.13 or later, and was the
CONFIG_INOTIFY option enabled when your kernel was compiled? If so,
something mysterious has gone wrong. Please e-mail radu.voicilas@gmail.com
and mention that you saw this message.
2014-09-09 13:07:23 UTC FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
The text was updated successfully, but these errors were encountered: