bfosberry
commented
7 years ago Hey! My understanding is that Jet assumes the folder is available locally like you mention. I think the best way around this is to share the volume from your linux docker machine vm to a similar location within your directory in windows.
Another option would be to ssh in using docker-machine, download jet and set up a workspace on the virtual machine.
markphelps
Hi, i tried to run 07.volumes on windows 7 with jet 1.17.0 and docker running with docker-machine on a vm, and i got the following:
{StepStarted=step_name:"bash_write_artifact.sh"} {BuildImageStarted=image_name:"demowrite" service_name:"write"} {BuildImageStdout=image_name:"demowrite" service_name:"write"}: Step 1 : FROM ubuntu {BuildImageStdout=image_name:"demowrite" service_name:"write"}: ---> 0ef2e08ed3fa {BuildImageStdout=image_name:"demowrite" service_name:"write"}: Step 2 : ADD . /app {BuildImageStdout=image_name:"demowrite" service_name:"write"}: ---> Using cache {BuildImageStdout=image_name:"demowrite" service_name:"write"}: ---> b98e81b010ff {BuildImageStdout=image_name:"demowrite" service_name:"write"}: Step 3 : WORKDIR /app {BuildImageStdout=image_name:"demowrite" service_name:"write"}: ---> Using cache {BuildImageStdout=image_name:"demowrite" service_name:"write"}: ---> 45184db63145 {BuildImageStdout=image_name:"demowrite" service_name:"write"}: Successfully built 45184db63145 {BuildImageFinished=image_name:"demowrite" service_name:"write"} {StepFinished=step_name:"bash_write_artifact.sh" type:STEP_FINISHED_TYPE_ERROR} API error (500): {"message":"Invalid volume spec \"c:\\\\dev\\\\code\\\\3rd\\\\codeship-tool-examples\\\\07.volumes\\\\tmp:/artifacts\": invalid mode: /artifacts"}I think jet assumes that the host path in the volumes declaration in the codeship-services.yml (./tmp) is a local (windows) path:data: image: busybox volumes:
but in my case is a path in the VM running rocker which is linux. Is there any way to work around this? Is jet compatible with docker-machine?