error when used with docker-machine

[kumavis]

all other containers booted correctly

ERROR: for prometheus  Cannot start service prometheus: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/home/xyz/Development/ethereum2-docker-compose/config/prometheus/prometheus-p.yaml\\\" to rootfs \\\"/var/lib/docker/overlay2/0859d586e611218284bc2e0a6cc0cb53ef1dba7598b9a9fd54d41d1d36c76993/merged\\\" at \\\"/var/lib/docker/overlay2/0859d586e611218284bc2e0a6cc0cb53ef1dba7598b9a9fd5``4d41d1d36c76993/merged/etc/prometheus/prometheus.yml\\\" 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

ethereum2-docker-compose on  master [!?] 
⇡0% ➜ docker -v
cokecDocker version 19.03.4-rc1, build 4ba2b1c606

ethereum2-docker-compose on  master [!?] took 2s 
⇡0% ➜ docker-machine -v
docker-machine version 0.16.0, build 702c267f

no volumes currently

ethereum2-docker-compose on  master [!?] took 3s 
⇡0% ➜ docker volume ls                       
DRIVER              VOLUME NAME

[kumavis]

likely related to this https://medium.com/@gnowland/unique-remote-local-volume-paths-with-docker-machine-40a4e369bcac

[kumavis]

worked around with

docker-machine scp -d -r ./data eth2-03:/var
docker-machine scp -d -r ./config eth2-03:/var

then changing source path of volumes from relative to /var/data /var/config

[stefa2k]

Hi, thank you for bringing this issue up! Right now focus is not on tools like docker-machine, but I'd be glad to include instructions and/or configs for it if you can provide them in a pull request.

[kumavis]

@stefa2k i can tell there will be a few incompatibilities still, ill continue to report them

[stefa2k]

Yeah I'm pretty sure there will be inconsistencies along the way, same with docker swarm. Thanks for keeping us up to date!