You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: I believe that the push command could do a better job of handling untagged images. Currently, when a user tries to push an untagged image with no Default Registry set, the image is pushed to docker.io/library which is likely to be denied. Even if a default registry is set, the user is prompted to tag their image before pushing it and then must click Tag. Image shown below
My proposal: If an image isn't already tagged with a strict registry path, I believe clicking the push command should trigger the command pallete in which the user can select a container registry from any of the registries they are connected to and have the option of creating an ACR (if they are connected to Azure) if they don't have one already. This will help the user tag their image properly before pushing it to their registry of choice.
The text was updated successfully, but these errors were encountered:
Problem: I believe that the push command could do a better job of handling untagged images. Currently, when a user tries to push an untagged image with no Default Registry set, the image is pushed to docker.io/library which is likely to be denied. Even if a default registry is set, the user is prompted to tag their image before pushing it and then must click Tag. Image shown below
My proposal: If an image isn't already tagged with a strict registry path, I believe clicking the push command should trigger the command pallete in which the user can select a container registry from any of the registries they are connected to and have the option of creating an ACR (if they are connected to Azure) if they don't have one already. This will help the user tag their image properly before pushing it to their registry of choice.
The text was updated successfully, but these errors were encountered: