microsoft / microsoft/vscode-remote-release

Devcontainer VSCode freezes while activating extensions

Open
#11,449 0 comments 1 reaction 2 assignees View on GitHub

@alexr00 is already working on this.

Since Jan 23, 2026.

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

Description

  • VSCode Version: 1.108.1
  • Local OS Version: Ubuntu 22.04
  • Remote OS Version: ubuntu:noble
  • Remote Extension/Connection Type: Dev Containers
  • Logs:
==> main.log <==
2026-01-22 18:29:18.470 [info] Extension host with pid 139377 exited with code: 0, signal: unknown.

==> editSessions.log <==
2026-01-22 18:29:24.912 [info] Prompting to enable cloud changes, has application previously launched from Continue On flow: false

==> main.log <==
2026-01-22 18:30:25.323 [error] CodeWindow: detected unresponsive
2026-01-22 18:30:46.350 [error] CodeWindow: detected unresponsive

Steps to Reproduce:

  1. Im using this devcontainer https://github.com/nextcloud/server/tree/master/.devcontainer
  2. With a different devcontainer.json
{
	"name": "NextcloudServer",
	"dockerComposeFile": "docker-compose.yml",
	"service": "nextclouddev",
	"postCreateCommand": ".devcontainer/setup.sh",
	"postStartCommand": ".devcontainer/postStart.sh",
	"forwardPorts": [
		80,
		443,
		8080,
		8025
	],
	"customizations": {
		"vscode": {
			"extensions": [
				"bmewburn.vscode-intelephense-client",
				"ms-azuretools.vscode-docker",
				"xdebug.php-debug",
				"donjayamanne.githistory"
			],
			"settings": {
				"php.suggest.basic": false
			}
		}
	},
	"workspaceFolder": "/var/www/html",
	"remoteUser": "devcontainer"
}

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

check #9943

Window is stuck at this state

Image

and not responding anymore

Image

To get it working again you need to clean the database as indicated in the following comment https://github.com/microsoft/vscode-remote-release/issues/9943#issuecomment-2322255981

This happens due to port forwarding, currently i have this ports in my json:

        "dockerComposeFile": "docker-compose.yml",
	"forwardPorts": [
		80,
		443,
		8080,
		8025
	],

and this ports in my docker compose

    ports:
      - 80:80
      - 443:443
      - 8080:8080
      - 8025:8025

Rows in database:
SELECT * FROM ItemTable WHERE key LIKE 'remote.tunnels.toRestore%';

key: 

remote.tunnels.toRestore.dev-container+7b22686f737450617468223a222f686f6d652f63617261632f70726f6a656374732f736572766572222c226c6f63616c446f636b6572223a66616c73652c22636f6e66696746696c65223a7b22246d6964223a312c22667350617468223a222f686f6d652f63617261632f70726f6a656374732f7365727665722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c2265787465726e616c223a2266696c653a2f2f2f686f6d652f63617261632f70726f6a656374732f7365727665722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c2270617468223a222f686f6d652f63617261632f70726f6a656374732f7365727665722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c22736368656d65223a2266696c65227d7d.-1577481295

value:
[{"remoteHost":"0.0.0.0","remotePort":80,"localAddress":"[::1]:80","localUri":{"$mid":1,"path":"/","scheme":"http","authority":"[::1]:80"},"protocol":"http","source":{"source":2,"description":"Dev Containers"}},{"remoteHost":"0.0.0.0","remotePort":8080,"localAddress":"[::1]:8080","localUri":{"$mid":1,"path":"/","scheme":"http","authority":"[::1]:8080"},"protocol":"http","source":{"source":2,"description":"Dev Containers"}},{"remoteHost":"0.0.0.0","remotePort":8025,"localAddress":"[::1]:8025","localUri":{"$mid":1,"path":"/","scheme":"http","authority":"[::1]:8025"},"protocol":"http","source":{"source":2,"description":"Dev Containers"}},{"remoteHost":"localhost","remotePort":443,"localPort":39447,"localAddress":"localhost:39447","localUri":{"$mid":1,"path":"/","scheme":"https","authority":"localhost:39447"},"protocol":"https","source":{"source":2,"description":"Dev Containers"}}]
key:

remote.tunnels.toRestoreExpiration.dev-container+7b22686f737450617468223a222f686f6d652f63617261632f70726f6a656374732f736572766572222c226c6f63616c446f636b6572223a66616c73652c22636f6e66696746696c65223a7b22246d6964223a312c22667350617468223a222f686f6d652f63617261632f70726f6a656374732f7365727665722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c2265787465726e616c223a2266696c653a2f2f2f686f6d652f63617261632f70726f6a656374732f7365727665722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c2270617468223a222f686f6d652f63617261632f70726f6a656374732f7365727665722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c22736368656d65223a2266696c65227d7d.-1577481295

value:

1770301165226

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.