-
Notifications
You must be signed in to change notification settings - Fork 511
PowerShell extension fails to start inside container #3466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Milestone
Comments
That looks like a pretty clear cut bug! I'll try to reproduce. Thanks for the report. |
5 tasks
This reproed for me today
|
@SydneyhSmith do you have any more detailed logs? Would love to know what the server said. |
Retested and got it running no problem 😄 -- looks resolved to me |
Hurray! |
This issue has been marked as fixed. It has been automatically closed for housekeeping purposes. |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Prerequisites
Summary
When attaching VSCode to a container, using the Remote - Containers extension, an exception is thrown in the logs, and the extension fails to startup. I'm using Docker Desktop to spin up a PowerShell 7.1.3 container "locally," and then attempting to attach to it.
PowerShell Version
Visual Studio Code Version
Extension Version
[email protected]
Steps to Reproduce
docker run --rm --interactive --tty mcr.microsoft.com/powershell
Attach to Running Container
commandStarting PowerShell...
text stays active in lower-right corner of VSCode window.Visuals
Logs
The text was updated successfully, but these errors were encountered: