-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nomad can't use relative directories in Docker binds in 0.9.2 on Windows #5798
Comments
@damoxc Can you porvide the job spec, particularly if You are correct |
@notnoop I can, however the error seems to be coming from Here's the relevant section from a
|
I've just been debugging and stepping through the Go code above, using the relative path format causes the Docker parser to flag the source as a volume instead of a bind mount. As it has decided it is a volume not a bind, then it uses https://github.com/moby/moby/blob/master/volume/mounts/windows_parser.go#L261-L274 for validation. The section above for bind mount validation has a call to assert that the path source is an absolute path. |
@damoxc thank you so much! So I misunderstood where the error is coming from - we'll investigate and follow up. |
Hey there Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this. Thanks! |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.9.2 (028326684b9da489e0371247a223ef3ae4755d87)
Operating system and Environment details
Server: Ubuntu 18.04
Client: Windows Server 2019 / Docker 18.09.6
Issue
Relative binds now no longer work under Windows due to the switch to use the Docker volume parser which expects a full path for source and destination.
Reproduction steps
Attempt to use a relative directory in a docker volume spec. The below bit of Go also exhibits the problem:
Job file (if appropriate)
I can supply an example if necessary but seems superfluous.
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: