8000 Find ways to ease the transition from Docker to Container Tools · Issue #41 · microsoft/vscode-containers · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Find ways to ease the transition from Docker to Container Tools #41

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
Open
6 of 9 tasks < 8000 /div>
bwateratmsft opened this issue Apr 14, 2025 · 4 comments
Open
6 of 9 tasks

Find ways to ease the transition from Docker to Container Tools #41

bwateratmsft opened this issue Apr 14, 2025 · 4 comments
Assignees
@fiveisprime @bwateratmsft
Milestone
2.0.2

Comments

@bwateratmsft
Copy link
Collaborator
bwateratmsft commented Apr 14, 2025 •
edited
Loading

Users will be jarred by the transition from Docker to Container Tools if we aren't careful. We should consider making it clear in a lot of ways what's happening:
@bwateratmsft bwateratmsft added this to the 2.0.0 milestone Apr 14, 2025
@fiveisprime
Copy link
Member

I'd like to get a toast notification in vscode-docker and give some time for folks to create issues and ask questions. I want to make sure we understand and address any concerns as soon as possible.

@realsircodesalot
Copy link

Depending on release, I would also recommend this getting mentioned in the following vscode update release notes. While there are several of us following a number of related tickets on GitHub, there are possibly some that aren't. Additionally, it should be considered, that many may have disabled vscode-docker extension auto updates & locked it in on an older version that still displays containers/images etc while using podman.

@bwateratmsft bwateratmsft modified the milestones: 2.0.0, 2.0.1 Apr 21, 2025
@rlipscombe
Copy link

Something else:

  • Something prompted me to install Container Tools.
  • Container Tools prompted me to uninstall the Docker extension, which I did.
  • A day later, VS Code prompted me to reinstall the (recommended) Docker extension, which I did.
  • This broke Container Tools.

Perhaps that recommendation should be disabled/removed?

Oh, and the Docker extension in Marketplace should have a clear "deprecated" warning at the top.

@bwateratmsft
Copy link
Collaborator Author
bwateratmsft commented Apr 30, 2025 •
edited
Loading

Thanks for reporting this @rlipscombe. We have a change in the upcoming VSCode Insiders build (which will reach stable early next month when they release) to fix the issue with your third bullet--VSCode will no longer recommend the Docker extension when the Container Tools extension is already installed.

As for deprecation--we don't plan to actually deprecate the Docker extension (at least not any time soon), but instead we're going to turn it into an extension pack that contains Container Tools--this will migrate users who do not opt in with the toast now.

@bwateratmsft bwateratmsft modified the milestones: 2.0.1, 2.0.2 May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fiveisprime fiveisprime

@bwateratmsft bwateratmsft

Labels
None yet
Projects
None yet
Milestone
2.0.2
Development

No branches or pull requests
4 participants
@rlipscombe @realsircodesalot @fiveisprime @bwateratmsft
0