-
Notifications
You must be signed in to change notification settings - Fork 445
Fixes #1357 #1358
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
base: main
Are you sure you want to change the base?
Fixes #1357 #1358
Conversation
…' to 'ms-azuretools.vscode-containers' in Docker features
@microsoft-github-policy-service agree |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @labiraus ,
Thank you for the contribution. Would you kindly site any official documentation which suggests that ms-azuretools.vscode-docker
extension has been superseded by ms-azuretools.vscode-containers
?
From what I gather, the former is the extension to enable docker cli whereas the latter is the devcontainers extension. Kindly let me know if I am missing some important points here.
With Regards,
Kaniska
@labiraus according to this blog post, the existing Docker extension is becoming Container Tools |
As @charsleysa has highlighted, the docker extension is being superseded by the container extension. If you download both onto your machine then the container extension will pop up with an error telling you to remove the docker extension. Both the docker extension and container extension provide the same functionality. You may be confusing ms-azuretools.vscode-containers (container extension) with ms-vscode-remote.remote-containers (devcontainer extension) |
Hello @labiraus , Thank you for the clarification. Indeed that seems to be the case that With Regards, |
Update VS Code extension references from 'ms-azuretools.vscode-docker' to 'ms-azuretools.vscode-containers' in Docker features