stepchowfun/toast

When using remote DOCKER_HOST, cannot mount paths

lynaghk opened this issue · 1 comments

Since Toast uses Docker bind mounts to bring files into a container, tasks with mount_paths will fail as the remote Docker engine specified by the DOCKER_HOST environment variable won't have those paths:

[ERROR] Unable to create container.
Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /Users/dev/work/incubator/container-workflow-test/foo.html

Not sure what options are for supporting this use case (or if it's desired at all), but thought it would be worth mentioning.

Thanks for filing this bug report. This is expected due to the way Docker works (bind mounts, as you mentioned). There's not really anything we can do (without implementing some kind of file system synchronization scheme ourselves).