Skip to content
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

MSYS2_ARG_CONV_EXCL doesn't work the way i expected #1130

Open
SvenDowideit opened this issue Feb 2, 2018 · 2 comments
Open

MSYS2_ARG_CONV_EXCL doesn't work the way i expected #1130

SvenDowideit opened this issue Feb 2, 2018 · 2 comments

Comments

@SvenDowideit
Copy link

I have a bash script that has lines like:

export MSYS2_ARG_CONV_EXCL="/mnt;/home;/usr;/var;/tmp;/etc"
mkdir -p /mnt/${vol}
${RUN} docker volume create --opt type=none --opt device=/mnt/${vol} --opt o=bind ${vol}

the name munging is prevented for the mkdir case, but not the docker volume case

I can get the result I need, by adding device=/ to MSYS2_ARG_CONV_EXCL

but I thought I'd confirm if this is correct, or an bug.

@mati865
Copy link
Collaborator

mati865 commented Feb 2, 2018

MSYS2_ARG_CONV_EXCL is a semi-colon separated env. var that MSYS2 compares each part of with the front of each argument.
https://stackoverflow.com/questions/26185684/msysgit-bash-shell-thinks-argument-is-a-unc-path-when-its-not

More info here

@rkitover
Copy link
Contributor

rkitover commented Mar 13, 2018

Just ran into this myself, with docker as well.

EDIT: I'm trying to pass --volume builds:/data or --mount source=builds,target=/data to docker run and nothing that I've tried to set MSYS2_ARG_CONV_EXCL to works, anyone have any ideas?

EDIT 2: never mind, my issue is actually #411

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants