Devcontainer VSCode freezes while activating extensions (Mac OS) #9943
Assignees
Labels
containers
Issue in vscode-remote containers
info-needed
Issue requires more information from poster
Comments
|
Which version of Docker Desktop are you running? Is there more information in the renderer or local extension host Output channels? |
This comment has been minimized.
This comment has been minimized.
|
I can't see the output channels in the terminal because the window freezes. I then get a message from vscode that it is not responding and it returns to a local vscode window. So it is not clear which parts of the log are due to it cancelling and closing, or re-opening locally. There is a renderer.log in /Users/user/Library/Application Support/Code/logs/20240705T111321/window19/renderer.log exthost.log In the remote containers log, everything looks successful |
|
If I rename my workspace directory and rebuild it works the first time. If I close it and open it again it gets stuck on activating extensions. So I have to rename the folder each time I want to launch the devcontainer. Alternatively, I can launch the container manually through Docker and attach vscode to it through the vscode docker extension and then it will launch without getting stuck on "activating extensions". |
|
Can you try to trigger |
|
There are no extensions listed in the devcontainer.json or default extensions in the devcontainer settings or in the docker image referenced by the docker-compose.yml. I can't get to F1 > Developer: Reload with extensions disabled in the devcontainer because the window freezes. Although the vscode window freezes, the docker containers remain up until I kill the frozen window. So I can inspect the containers & volumes if theres anything of interest there? |
|
Could you share the devcontainer.json? Also retry with the recently released Dev Containers 0.375.1 which comes with two important fixes (though these bugs shouldn't freeze the window). |
|
I have updated vscode and still get the frozen window. The containers are built for linux/arm64 but I have the same problem when built for other platforms and using Rosetta. The containers build ok and are still running while the window freezes. I can connect vscode to the container without the window freezing if I connect via the Docker extension and select "Attach Visual Studio Code". devcontainer.json: docker-compose.yml: The docker-compose file is in the .devcontainer directory and references the workspace which is a level up |
|
What is the base image (distro and version) of wp-development-arm64:8.0? Worth a try: Remove the 3 default entries from the following user setting and rebuild the dev container: |
|
@chrmarti The base image is php:8.1-apache + some extra requirements Thanks for the suggestion. I had already emptied the list of default extensions. |
|
Could you also check the Remote Extension Host's log? Make sure to not only empty "Default Extensions", but also "Default Extensions If Installed Locally". These are shown as being installed in the log you posted. |
I cleared the logs folder on the host and launched the devcontainer until it froze. These are the logs from the session. |
|
Could you also check The above logs don't seem to show the freeze yet? |
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
vs-code-engineering
bot
closed this as not planned
I just wanted to chime in and say I've been struggling with the exact same problem on my Mac for months. It happens for every different Dev Container I have. The VS Code window locks up during the "Activating Extensions" phase (container starts just fine). Manually attaching to the container via the Docker extension is my workaround too. |
|
I narrowed the issue down to a To fix the issue I had to remove port forwarding for ports 80 and 443 in the devcontainer.json and delete the I also have port mappings for 80 & 443 in my docker-compose.yml so perhaps there was a conflict. I could see that 443 was being automatically mapped to a high port number in I could not see an error message and the window was freezing after launching the devcontainer while "Activating extensions" was spinning in the status bar. I'm not sure what the connection is to the remote extension host, if any, perhaps it was trying to communicate through the https 443 port that had been re-mapped. |
|
@david02871, you have changed my life! This appears to have sorted out my problems with multiple devcontainers. Thanks so much!! |
|
@david02871 @anthonyeden Do you have a simple example and precise steps to reproduce the problem? |
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
vs-code-engineering
bot
closed this as not planned
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm unable to launch a previously working devcontainer which now freezes with the "Activating extensions.." stage showing in the status bar.
I can't see any errors. Could it be that the error will be in 'Output: Extension Host (remote)'? I can't open that log because the window freezes. Are there any other ways to view it?
The last part of 'Dev Containers Developer > Show all logs' is:
I have tried the following in my devcontainer.json:
The text was updated successfully, but these errors were encountered: