microsoft / microsoft/vscode-remote-release

DevContainers wont shutdown after Remote Connection is closed or after quitting VSCode

Open
#8,991 5 comments 23 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Dec 13, 2024.

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

Description

  • VSCode Version: 1.82.2
  • Local OS Version: MacOS 13.2.1 (22D68)
  • Remote OS Version: node:18
  • Remote Extension/Connection Type: Containers

Containers wont shutdown in MacOS when VSCode is shut down or remote session is closed. This happens irrespective of whether "shutdownAction" is explicitly set as "stopContainer", (or is just not mentioned). The containers keep running, when they should have shutdown.

  • Logs:

Steps to Reproduce:

  1. Setup DevContainers as per tutorial, using existing Dockerfile
  2. Add "shutdownAction": "stopContainer", explicitly in devcontainer.json file
  3. Start the remote-container session, or rebuild devcontainer (remote session starts successfully)
  4. Either Quit VSCode or select "Close Remote Connection" in Dev Containers Command Palette & wait for 30-60 seconds

Does this issue occur when you try this locally?: Not applicable
Does this issue occur when you try this locally and all extensions are disabled?: Yes

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.