Problems using volumes and/or data-only containers. about ghost HOT 4 CLOSED

Probably because the daemon does not have write permissions on whatever $PWD/tmp maps to.

from ghost.

Are you referring to the docker daemon? It has full permission to read the directory...Or are you referring to another daemon service?

It works perfectly well with the official docker ghost image to do this (using /var/lib/ghost, which is what they uses). That's where I got the expected output from.

from ghost.

By daemon I am referring specifically to /usr/bin/ghost (node) running in the container. I'm not really sure why file permissions would ever be an issue since the daemon runs as root and Docker also runs as root but I don't know what else to suggest. I am running this image in production using similar volume mapping so all I can tell you is that it works for me.

from ghost.

Ok. I moved to another blogging platform in the end... I also do not know the caused the issue, but I am fine with you closing it as can not reproduce.

from ghost.