DockerHost (no email address needed, only user name and password) The solution was a combination of suggestions I found on the internet - given that the directory you want to share is below your user directory:
#WINDOWS 10 DAEMON TOOLS ACCESS DENIED WINDOWS 10#
I struggled with this issue on Windows 10 for quite some time. I admit I'm leaning toward the latter because I can find no documentation about this anywhere. I don't know if this is a bug, a bad interaction between current windows & docker, or something I've done wrong locally. I've compared the settings in docker, on the virtual networks, on the directories between home and work - the only differences I can find are because work is on a Domain, and has a different username, and that my version of windows is 1607. Mounting directories definitely works, I've run the alpine ls /data example shown on the settings for shared drives in Docker for Windows. If I make the directory myself, and run docker-compose.yml again, I get this error:īlog_1 | chown: changing ownership of '/var/lib/ghost': Permission denied On my work machine, it creates the blog directory, and populates it with the themes and content as expected from a ghost blog.ĮRROR: for blog Cannot start service blog: error while creating mount source path '/C/Users/joe/Projects/site/blog': mkdir /C/Users/joe/Projects/site/blog: permission deniedĮRROR: Encountered errors while bringing up the project. Typically Windows can get around this if your user account has administrative privileges, but for some reason this simply doesn. Place the docker-compose.yml file below the directory:.Create a Project\site directory in C:\users\joe\.sc config docker binpath ''C:Program Filesdockerdockerd.exe' -run-service -H tcp://0.0.0.0:2375'. Run the following command in a command prompt (cmd.exe not PowerShell): cmd. Using this method, Docker Engine flags are set directly on the Docker service.
#WINDOWS 10 DAEMON TOOLS ACCESS DENIED UPDATE#
I'm running the Creator update of Windows 10, and the latest Docker for Windows (ie, Windows 10 Pro versin 1703, and Docker version 17.03.1-ce-win5)Īs a test, I followed this procedure, at both home and work (where I'm on the previous version of windows 10): The Docker Engine can also be configured by modifying the Docker service with sc config. The ghost docker image mounts the drive fine, but when it tries to chown the file, it gets a permission denied error. Since one of the goals of my project is to develop themes and other things with live data, I've created a volume mount for the /var/lib/ghost directory as suggested by the ghost docker image. I'm working on developing a ghost blog and deploying it as a docker container.