Error wile building with docker-compose

[sethokayba]

Hi,

I am trying the first build in the book page 51 :

I am executing the lines :

git clone https://github.com/backstopmedia/kong-book-example cinema-3
cd cinema-3
docker-compose up

but getting errors at the console : (by the way, i am running docker on windows 10, Linux Containers)

Creating cinema-3_bookings_1 ... done
Creating cinema-3_movies_1 ... done
Creating cinema-3_showtimes_1 ... done
Creating cinema-3_kong-postgres_1 ... done
Creating cinema-3_kong-migration_1 ... done
Creating cinema-3_users_1 ... done
Creating cinema-3_kong_1 ...
Creating cinema-3_nginx_1 ... error

ERROR: for cinema-3_nginx_1 Cannot start service nginx: b'OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/host_mntCreating cinema-3_kong_1 ... done
1e77938e17f2e0f62e/merged/etc/nginx/nginx.conf\\\" caused \\\"not a directory\\\"\"": unknown: 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 nginx Cannot start service nginx: b'OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/host_mnt/d/kong/cinema-3/nginx.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/4e6d9ddaf7a7280613485a6e4f0d1d488e9e81221439241e77938e17f2e0f62e/merged\\\" at \\\"/var/lib/docker/overlay2/4e6d9ddaf7a7280613485a6e4f0d1d488e9e81221439241e77938e17f2e0f62e/merged/etc/nginx/nginx.conf\\\" caused \\\"not a directory\\\"\"": unknown: 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'
Encountered errors while bringing up the project.

Thank you in advance.
Kindly.

[xav-b]

Hi @sethokayba, sorry about the trouble. It seems like the way we mount the volume in the docker-compose.yml file is very UNIX specific and breaks on Windows. Could you try the fix proposed on this thread and let us know if it worked for you?