Host Path Of Volume
Ah, very good point! There is no warning. Should non-absolute paths error out by default, only allowed via an option? In my use-case, filling / with empty directories is not very useful, but I can see how it could be useful in controlled circumstances. Pewter:docker (master) root$ ls -d /contrib ls: cannot access /contrib: No such file or directory pewter:docker (master) root$ docker run -v contrib:/tmp/contrib debian:jessie ls /tmp/contrib pewter:docker (master) root$ ls -d /contrib /contrib pewter:docker (master) root$ touch /contrib/file pewter:docker (master) root$ docker run -v contrib:/tmp/contrib debian:jessie ls /tmp/contrib file. Ah, very good point!
There is no warning. Should non-absolute paths error out by default, only allowed via an option? In my use-case, filling / with empty directories is not very useful, but I can see how it could be useful in controlled circumstances.
NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE task-pv-claim Bound task-pv-volume 10Gi RWO manual 30s Create a Pod The next step is to create a Pod that uses your PersistentVolumeClaim as a volume.
The Host Path Of The Shared Folder Is Missing
Pewter:docker (master) root$ ls -d /contrib ls: cannot access /contrib: No such file or directory pewter:docker (master) root$ docker run -v contrib:/tmp/contrib debian:jessie ls /tmp/contrib pewter:docker (master) root$ ls -d /contrib /contrib pewter:docker (master) root$ touch /contrib/file pewter:docker (master) root$ docker run -v contrib:/tmp/contrib debian:jessie ls /tmp/contrib file. Is there an open issue for relative volume mounts, or is it a 'won't fix'? If everyone on our team was on Linux or macOS, $PWD is a reasonable workaround but that doesn't work on Windows, and using%CD% on Windows is also not a 100% solution because some users might opt to use different shells than cmd.exe, and if that shell is something like Git Bash or MSYS2 shell, path conversion will kick in so $PWD will not end up being a valid path as received by Docker, etc. Is there a technical reason why -v.:/path could not be supported by Docker engine? It would make cross-platform invocation so much easier. Is there an open issue for relative volume mounts, or is it a 'won't fix'?
Host Path Of Volume Formula
If everyone on our team was on Linux or macOS, $PWD is a reasonable workaround but that doesn't work on Windows, and using%CD% on Windows is also not a 100% solution because some users might opt to use different shells than cmd.exe, and if that shell is something like Git Bash or MSYS2 shell, path conversion will kick in so $PWD will not end up being a valid path as received by Docker, etc. Is there a technical reason why -v.:/path could not be supported by Docker engine? Iq options platform. It would make cross-platform invocation so much easier. Thanks for the pointer. I'm still confused though: the first paragraph on that page mentions that relative paths should be supported: When you use a bind mount, a file or directory on the host machine is mounted into a container. The file or directory is referenced by its full or relative path on the host machine. That doesn't seem to be the case though: $ docker run --rm -it --mount type=bind,source=example,target=/tmp/mounted ubuntu /bin/bash C: Program Files Docker Docker Resources bin docker.exe: Error response from daemon: invalid mount config for type 'bind': invalid mount path: 'example' mount path must be absolute.