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

Ability to disable automatic start of Docker #9773

Closed
npalmius opened this issue Apr 12, 2024 · 4 comments
Closed

Ability to disable automatic start of Docker #9773

npalmius opened this issue Apr 12, 2024 · 4 comments
Assignees
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@npalmius
Copy link

npalmius commented Apr 12, 2024

The following was added in the March 2024 (version 1.88) VS Code release:

Automatic start of Docker

When the Dev Containers extension detects that Docker is not running on Windows or Mac, it now checks for and automatically starts Docker Desktop. This should avoid a common manual step after rebooting your machine.

I often use multiple VS Code instances - some using dev containers, some not.

Docker can be very resource intensive (especially because I have some large docker compose projects that start automatically when Docker starts), so sometimes I just want to open VS Code without Docker running so that I can use the VS Code instances that aren't using dev containers. The ones that need dev containers fail to load, but that's ok for me as I just need to start Docker then reload the window if I want to use them (this way I can also let the docker compose projects start before starting the dev container(s) that I want). It also means that I can load just the specific dev container(s) that I need for whatever I'm doing - I may have had other dev containers open when I last exited VS Code that I don't want to load.

However, after this update Docker automatically starts when starting VS Code. This starts some large docker compose projects, and then loads all the dev containers that I happened to have open when I last exited VS Code. If I'm not plugged in, this is particularly undesirable.

So it would be great to have an option to disable the automatic start of Docker. I have looked through the Dev Containers settings and couldn't find anything - apologies if I missed it.

@vscodenpa vscodenpa added the containers Issue in vscode-remote containers label Apr 12, 2024
@devdiogenes
Copy link

It often happen to me, when I open vscode after closing in a docker project. The vscode tries to open inside container, and start it even if I don't want to use

@chrmarti chrmarti added the feature-request Request for new features or functionality label Jul 31, 2024
@vscodenpa vscodenpa added this to the Backlog Candidates milestone Jul 31, 2024
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@joshspicer
Copy link
Member

Looking into adding a setting for the work that was done here: #9687

@joshspicer joshspicer modified the milestones: Backlog, August 2024 Jul 31, 2024
@joshspicer
Copy link
Member

This shipped in v0.382.0 (pre-release) with a new setting. Please let us know if the change helps!

Image

@joshspicer joshspicer added the verification-needed Verification of issue is requested label Aug 26, 2024
@rzhao271 rzhao271 added the verified Verification succeeded label Aug 27, 2024
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Oct 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

6 participants