Skip to content

Conversation

@mnowster
Copy link

Should fix #2128

They should not ever be relative.

Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>
splitdrive doesn't handle relative paths, so if volume_path contains
a relative path, we handle that differently and manually set drive to ''.

Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>
@dnephin
Copy link

dnephin commented Oct 13, 2015

LGTM

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wait, why is this removed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because container_path should never be relative, so we don't need to call expanduser on it. @aanand spotted it last time when I was working through understanding the paths situation.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it would expand to the wrong path, that's true. We added this in 1.4.0, so we should probably call this out in the release notes as a bug fix.

dnephin added a commit that referenced this pull request Oct 14, 2015
…relative-paths

2128 split drive not handling relative paths
@dnephin dnephin merged commit b9c76df into docker:master Oct 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Relative path, .:/data, does not work on windows

3 participants