Skip to content
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

Mounting Error using Docker Toolbox #3

Closed
bholbrook73 opened this issue Jul 20, 2017 · 2 comments
Closed

Mounting Error using Docker Toolbox #3

bholbrook73 opened this issue Jul 20, 2017 · 2 comments

Comments

@bholbrook73
Copy link

On Windows 10 Home using docker Toolbox and a stock clone of docker-nginx-php-mysql, the following error occurs when using the docker-compose up -d command.

ERROR: for ninjacat_web_1  Cannot start service web: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/d/development/projects/ninjacat/etc/nginx/default.conf\\\" to rootfs \\\"/mnt/sda1/var/lib/docker/aufs/mnt/01f058ca3728ad3150eaa198b05a3fdc63914b0274dc03db873a8b11d475b0df\\\" at \\\"/mnt/sda1/var/lib/docker/aufs/mnt/01f058ca3728ad3150eaa198b05a3fdc63914b0274dc03db873a8b11d475b0df/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\""
: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for web  Cannot start service web: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/d/development/projects/ninjacat/etc/nginx/default.conf\\\" to rootfs \\\"/mnt/sda1/var/lib/docker/aufs/mnt/01f058ca3728ad3150eaa198b05a3fdc63914b0274dc03db873a8b11d475b0df\\\" at \\\"/mnt/sda1/var/lib/docker/aufs/mnt/01f058ca3728ad3150eaa198b05a3fdc63914b0274dc03db873a8b11d475b0df/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\""
: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
@nanoninja
Copy link
Owner

Hello, @bholbrook73

I do not work on Windows and I can not do tests with a similar environment yet. The problem may be paths in the "docker-compose.yml" file. The absolute paths on Windows start with "C:\", maybe you should adapt them?

@Jehong-Ahn
Copy link

Jehong-Ahn commented Apr 5, 2018

@bholbrook73, you may missed some files for the first run.
Try docker-machine restart && docker-compose up -d.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants