-
Notifications
You must be signed in to change notification settings - Fork 286
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
Updater expands variables in the PATH environment variable #859
Comments
It'll be fixed for next update. Thanks for the report. |
Just updated to new version and now the
|
@nlaplante : Strange, is |
Hi! I just updated to the new edge version (details below). The changelog stated this was fixed, but the problem still persists. My PATH was changed to have all variables expanded just like the example I gave in the original report. Version 17.06.1-ce-rc1-win20 (12818) |
I just found out that Thanks for your attention! |
I just updated to the new version and it seems to be fixed on this last update. Thanks! Version 17.07.0-ce-rc1-win21 (12927) |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
I believe this could be happening when executing the installer also, but I didn't test with the installer, just with the self-update feature.
If before executing the update you had your PATH set to, for example:
it will become:
after the update is done.
I just updated to the version posted below and experienced this issue. I actually have to update my PATH environment variable every time Docker releases an update. I use
%APPDATA%
in one of my paths, which is user dependant, so when it is expanded it becomesC:\Users\<username>\AppData\Roaming
setting it to the current user which is not what I intended.If you need more information, just tell me and I will try to provide it. Thanks!
Version 17.06.0-ce-win17 (12626)
Channel: edge
4bb7a7d
The text was updated successfully, but these errors were encountered: