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.

Sign up for GitHub

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

Jump to bottom

Cannot connect private registries anymore #4140

Closed
LordMilutin opened this issue Oct 26, 2023 · 9 comments · Fixed by #4143
Closed

Cannot connect private registries anymore #4140

LordMilutin opened this issue Oct 26, 2023 · 9 comments · Fixed by #4143
Labels
bug fix released registries
Milestone
1.28.0

Comments

@LordMilutin
Copy link

LordMilutin commented Oct 26, 2023 •
edited
Loading

I don't know what you did but private registries are no longer visible for connection...
There is no way anymore to connect them. Please bring back this functionality as this was my only way to manage the registry with a nice UI...

Originally posted by @LordMilutin in #869 (comment)
@bwateratmsft
Copy link
Collaborator

bwateratmsft commented Oct 26, 2023 •
edited
Loading

Do you mean generic V2 registries or some other private registry (GitLab, Docker Hub, etc.)?

@LordMilutin
Copy link
Author

Yeah, I am referring to V2 registries from the official registry image on DockerHub.
https://hub.docker.com/_/registry

@bwateratmsft
Copy link
Collaborator

We refactored the registry provider system to make it extensible, but V2 registries were and still are supported. The settings should have been migrated. Can you share a screenshot of your Registries view in the Docker explorer page?

@LordMilutin
Copy link
Author

Here you go. There is no option to specify a private docker registry nor enter username and pass.

image

image

@bwateratmsft
Copy link
Collaborator

bwateratmsft commented Oct 26, 2023 •
edited
Loading

Can you do "Connect to Generic Docker Registry..." in either the command palette or the context menu? Does anything happen?

Note, this is a different command from "Connect Registry"

@LordMilutin
Copy link
Author

Can you do "Connect to Generic Docker Registry..." in either the command palette or the context menu? Does anything happen?

Note, this is a different command from "Connect Registry"

Nothing at all happens...

@bwateratmsft
Copy link
Collaborator

Huh. Somehow you're in a strange state of data inconsistency where you're connected to the V2 registry provider but not to any individual V2 registries. This is definitely a bug.

I'm afraid there isn't any good workaround for this. There's a bad one--clearing out your entire memento storage by deleting or renaming %appdata%\Code\User\globalStorage\state.vscdb--but this will basically be like reinstalling VSCode from scratch. Your user settings will be preserved but all your accumulated temporary storage will be wiped out.

@bwateratmsft bwateratmsft added this to the 1.28.0 milestone Oct 26, 2023
@bwateratmsft bwateratmsft self-assigned this Oct 26, 2023
@bwateratmsft bwateratmsft mentioned this issue Oct 26, 2023
Merged
@bwateratmsft bwateratmsft removed their assignment Oct 26, 2023
@LordMilutin
Copy link
Author

Thank you Brandon!
I am on Linux, but I will go ahead and reinstall it anyway.

@bwateratmsft bwateratmsft mentioned this issue Nov 10, 2023
Closed
@bwateratmsft
Copy link
Collaborator

A fix has been released for this in Docker extension version 1.28.0.

@microsoft microsoft locked and limited conversation to collaborators Dec 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug fix released registries
Projects
None yet
Milestone
1.28.0
Development

Successfully merging a pull request may close this issue.

Allow disconnecting from generic registry V2 to escape broken state microsoft/vscode-docker
2 participants
@bwateratmsft @LordMilutin