-
Notifications
You must be signed in to change notification settings - Fork 283
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
Credential helpers are used even if they are not configured #6043
Comments
Create new issue since #5020 is closed |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
/lifecycle frozen /remove-lifecycle stale |
Why frozen? Bug is here |
Frozen means that it won't close this bug report automatically right? I did it to prevent the bot closing it without an answer from the docker dev team. |
The windows credentials store does not work for us, because our build script runs elevated: docker/cli#2682 (comment)
It works when I manually remove the Please either fix the bug that elevated shells can't login, or that |
[ X ] I have tried with the latest version of my channel (Stable or Edge)
Expected behavior
Docker should keep the config.json file untouched on every startup (esp. not insert/modify credStore value).
Actual behavior
On every startup, Docker modifies the config.json file on Windows, adding "credsStore":"desktop", which ultimatively leads to a situation in which it is not using the credentials stored in the config.json file in base64 encoding. In our use case, this is needed. In #1359, a checkbox has been introduced for Docker for Mac ("Securely store Docker logins in macOS keychain") to work around this issue. A solution would be to also introduce it for Docker for Windows. Alternatively, an option "credsStore":"none" would be an option which is persisted.
The text was updated successfully, but these errors were encountered: