-
Notifications
You must be signed in to change notification settings - Fork 514
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
docker error vs code #996
Comments
@stosc please add repro steps to this issue As an aside, #966 might've improved this experience - you're welcome to follow these instructions to try the latest build from master: https://aka.ms/azCodeInsiders |
Just ran into this issue myself when trying to add a private repository. Hardly any information is given in the window about the error. My repro steps:
Immediately the error is show that says nothing more than I have check that my login information works with I will give the Preview a chance and see if that helps. Looks like a significant improvement over the current extension. Let me know if you have any more questions |
FYI, this still does not work in the Preview build. Instead I am getting a different error: Is there any reason why a Gitlab docker registry wouldnt work? Also are registries that use a specific port supported? (i.e. |
Yeah you should be able to add a port. We only support basic auth registires right now. Does gitlab support basic auth or just OAuth? We're tracking the OAuth work here: #869 |
Not 100% sure what authentication method its using. Is there a way to test/confirm? It looks like Basic auth to me (simple username/password combo) instead of OAuth. In the past I have used |
Just to make sure - when you enter the address in VS Code you need to include the protocol like **https://**subdomain.domain.com:5000. Were you doing that?
I'm not familiar enough with gitlab to answer this. It's on the list to verify when we do #869 |
Yes, I included the protocol. VS Code actually enforces this before you can press Enter. I saw #869 earlier and am keeping track of the updates. I know I always hate this question but: Any idea on the timetable for that issue to be completed? Just looking for super rough estimate here (days, weeks, months, or years) to decide if I should wait or look at replicating the functionality on my own. Thanks for the help. |
I'm getting this exact error with http://cloud.canister.io:5000 using basic authentication. Docker Login from the command line passing username and password works fine. |
@mdemoret-nv I have some good new and some mildly bad news for you. The good news: I've just submitted two PRs to improve this area:
The mildly bad news is that I don't have any plans to add support for self-hosted GitLab any time soon. We would love if you could help contribute! Honestly it might be a simple change based on my above PRs, but I just don't have the time to created a self-hosted instance, test it, etc. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Repro steps:
Action: vscode-docker.connectCustomRegistry
Error type: ECONNRESET
Error Message: socket hang up
Version: 0.6.2
OS: win32
Product: Visual Studio Code
Product Version: 1.35.1
Language: zh-cn
Call Stack
The text was updated successfully, but these errors were encountered: