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

Prompting user to set Default Registry #1540

Closed
ucheNkadiCode opened this issue Jan 9, 2020 · 1 comment · Fixed by #1783
Closed

Prompting user to set Default Registry #1540

ucheNkadiCode opened this issue Jan 9, 2020 · 1 comment · Fixed by #1783

Comments

@ucheNkadiCode
Copy link
Contributor

After initially installing the Docker extension, building an image, and selecting the push command, docker push gives no prompt to set a default registry or to push to a specific registry (#1539). Instead, the user is forced to properly tag the image (someusername.azurecr.io/someexpressapp:latest) or else the container is pushed to docker.io by default. As a user aiming to push the image to Azure Container Registry, it was frustrating being met with this error multiple times.

image

If default registry has not been set, there should be prompting to either select a default or select a specific registry each time they push. The latter feature is discussed in #1539.

@dbreshears dbreshears added this to the 0.12.0 milestone Jan 10, 2020
@karolz-ms
Copy link
Contributor

@ucheNkadiCode like I mentioned in #1539, a tag is always required to push to any repository other than those hosted on docker.io. The concept of 'default registry' is something that does not currently exist in Docker in the sense that you are describing here.

My understanding is you are looking for a way to make working with registries easier. Let's brainstorm.

@bwateratmsft bwateratmsft self-assigned this Mar 13, 2020
@bwateratmsft bwateratmsft linked a pull request Mar 24, 2020 that will close this issue
@dbreshears dbreshears added P1 and removed P2 labels Mar 24, 2020
@bwateratmsft bwateratmsft removed their assignment Mar 30, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators May 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants