microsoft / microsoft/vscode-remote-release
reopen in devcontainer doesn't open after upgrade, Error: AttachConsole failed
Open
@chrmarti is already working on this.
Since Feb 13, 2026.
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.109.3
- Local OS Version:
- Remote OS Version:
- Remote Extension/Connection Type: Dev Containers/WSL/Remote - Tunnels/VS Code Server ms-vscode-remote.remote-containers-0.442.0
- Logs:
[2026-02-13T14:16:36.566Z] var consoleProcessList = getConsoleProcessList(shellPid);
[2026-02-13T14:16:36.567Z] ^
[2026-02-13T14:16:36.567Z] Error: AttachConsole failed
[2026-02-13T14:16:38.772Z] docker: Error response from daemon: accessing specified distro mount service:
[2026-02-13T14:16:39.892Z] trap "exit 0" 15
[2026-02-13T14:16:39.892Z] /usr/local/share/docker-init.sh
[2026-02-13T14:16:39.892Z] exec "$@"
[2026-02-13T14:16:39.892Z] Error: Command failed: docker run --sig-proxy=false -a STDOUT -a STDERR --mount source
Steps to Reproduce:
- open folder from vs code
- reopen in container
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.