This repository has been archived by the owner on Apr 7, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7
Better error prompt when Docker Desktop is installed #26
Labels
Comments
Closing this issue as it is resolved from the docker desktop side. |
It looks like this issue still exists. |
Related: We also need to check if the credentials helper binaries can be found before we use it. #68 (comment) I think it's better to address this problem in a separate issue, as it is quite complicated how native store is used and errors handled in |
This was referenced Jun 15, 2023
shizhMSFT
pushed a commit
that referenced
this issue
Jun 19, 2023
Resolves #26 Signed-off-by: Xiaoxuan Wang <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the version of your ORAS CLI
v0.16.0
What would you like to be added?
When Docker Desktop for Windows or macOS installed and is not currently running, running
oras
will encounter an error.It is better to have something like
It would be even better to give users an option to update the credential store. A sample output on Windows could be
Why is this needed for ORAS?
oras
in general does not requiredocker
ordockerd
.oras
reuses the docker config file and docker desktop sets the credential store to docker desktop when docker desktop is installed.Here are the scenarios for the complete behavior.
oras
on Linux without docker installed~/.docker/config.json
onoras login
.oras
on Linux with docker installed~/.docker/config.json
. If credential store is configured, oras also re-uses the credential store.~/.docker/config.json
. By default, it requires docker desktop running to run oras.~/.docker/config.json
and replacedesktop
withwincred
for thecredStore
field.desktop
withosxkeychain
.It would be better to let the users know what's the next steps, such as run Docker Desktop or update the config, when they encounter the weird pipe error.
Are you willing to submit PRs to contribute to this feature?
The text was updated successfully, but these errors were encountered: