Closed tmchartrand closed 6 months ago
Seeing Dev Containers 0.330.0 in VS Code 1.85.2
in the log. Could you update VS Code to 1.88 or later and Dev Containers to 0.363.0-pre-release or later and retry?
I think the older extension is the issue - I'm running older CentOS so can't update directly, but interestingly was able to install the newer extension for vscode-server on this machine when running through remote-ssh, and the problem was not present there. More motivation to upgrade the OS I guess, closing for now.
When trying to start a previously-built container from VS Code with the local workspace folder open (containing .devcontainer etc), the "Reopen in container" or rebuild and reopen commands fail silently, only adding a few
docker version
lines to the log. On the other hand, the "Open in container in current window" from the remote explorer context menu works fine.In a few cases I've also noticed odd behavior after trying this several times where simply opening the Remote Explorer tab seems to get the process unstalledl. This doesn't seem to reproduce consistently, but makes me wonder if it could be related to #9663.
Tested with the latest pre-release Dev Containers and Remote explorer extensions.
Steps to Reproduce:
I also noticed these lines in the previous shutdown log that could be related perhaps? shutdownMonitor-xxx.log
In some cases it gets further, showing the popup "Dev Container configuration already exists" and the following log:
Does this issue occur when you try this locally?: NA Does this issue occur when you try this locally and all extensions are disabled?: NA