microsoft / microsoft/vscode-remote-release

Start Docker daemon for me if it's not already started

Open
#8,089 1 comment 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Feb 22, 2023.

containers feature-request
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

I do not have Docker configured to start on machine boot, which means that I constantly hit the error message about "Make sure the Docker daemon is running". This adds friction to using local containers which is not present elsewhere in VS Code, e.g. we help users boot a codespace before they connect to an existing codespace, and we help users start a Jupyter kernel without requiring that one is already running.

I'd like the Dev Containers extension to start the Docker daemon for me when I first try to create a dev container, so that I don't have to manage Docker desktop all the time in order to use it in VS Code. I think this should be possible based on the docs but please correct me if I miss something here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.