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

Failed to add private Docker registry #470

Closed
sebastian-philipp opened this issue Sep 11, 2018 · 5 comments
Closed

Failed to add private Docker registry #470

sebastian-philipp opened this issue Sep 11, 2018 · 5 comments

Comments

@sebastian-philipp
Copy link

sebastian-philipp commented Sep 11, 2018

Hey,

when adding the registry:
http://10.17.3.0:5000
with no password to vscode, I'm getting the error mentioned below.

Repro steps:

  1. install vscode on Kubuntu via snap. (Interestingly, this failed to add a kmenu entry)
  2. install the docker extension
  3. click on Connect to private registry ... (preview)
  4. insert http://10.17.3.0:5000, <enter>
  5. <Enter> (no password)

Action: vscode-docker.connectCustomRegistry

Error type: Error
Error Message: The name org.freedesktop.secrets was not provided by any .service files

Version: 0.2.0
OS: linux, kubuntu 18.04

@StephenWeatherford
Copy link
Contributor

Can you successfully log in to docker hub in the extension (both use keytar that's installed with vscode)?

The following seem to suggest that installing gnome-keyring and libsecret might fix this:
lbryio/lbry-desktop#386
Foundry376/Mailspring#681

@sebastian-philipp
Copy link
Author

@StephenWeatherford actually, I didn't bother to add any credentials for docker hub, as I just wanted to use my local registry.

@StephenWeatherford
Copy link
Contributor

I was just trying to narrow down what worked and what didn't. Have you tried the suggested fix?

@sebastian-philipp
Copy link
Author

@StephenWeatherford Yes. sudo apt install gnome-keyring is a workaround. Turns out, after asking for the password of my private registry, vscode asks for a docker hub account credentials and then wants to create a new keyring.

I left the docker hub credentials empty and it still worked.

@StephenWeatherford
Copy link
Contributor

I glad it worked for you. Closing, but others can hopefully find the solution here if they need it.

@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants