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

Unable to start Container within PowerShell ISE - works fine in PowerShell #223

Closed
myfope opened this Issue Nov 11, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@myfope

myfope commented Nov 11, 2016

Expected behavior

When I open PowerShell ISE and run docker run -it microsoft/windowsservercore powershell it starts the container but hangs somewhere finally starting PowerShell.

Actual behavior

When I run docker ps I do see the started container. But it hangs at:

PS C:\Program Files\docker> docker run -it microsoft/windowsservercore powershell
�[2J�[H�[37;40mWindows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

and never shows the prompt for powershell. When I do the same within PowerShell (not ISE) it works just fine.

Information

  • Diagnostic ID from "Diagnose & Feedback" in the menu.
    Where can I find this on docker for Windows?

  • a reproducible case if this is a bug, Dockerfiles FTW
    Where can i find this on Docker for Windows?

  • page URL if this is a docs issue or the name of a man page

  • host distribution and version (Windows version, build number, etc)

Windows 10 1607 Build 14931.1002
docker version
Client:
Version: 1.13.0-dev
API version: 1.25
Go version: go1.7.3
Git commit: 72ec0f3
Built: Sat Oct 29 12:15:44 2016
OS/Arch: windows/amd64

Server:
Version: 1.13.0-dev
API version: 1.25
Go version: go1.7.3
Git commit: 72ec0f3
Built: Sat Oct 29 12:15:44 2016
OS/Arch: windows/amd64
Experimental: false

Steps to reproduce the behavior

  1. Start ISE as an Administrator
  2. docker run -it microsoft/windowsservercore powershell
@rn

This comment has been minimized.

Contributor

rn commented Nov 12, 2016

@myfope I can confirm that I can't get a interactive shell in ISE either. I suspecet ISE does not provide sufficient terminal emulation.

@friism is there anyone at Microsoft who could confirm this?

@friism

This comment has been minimized.

friism commented Nov 13, 2016

Yes, there are a well-documented problems with Powershell ISE, also see:

According to 22951 it was actually supposed to be fixed, so pinging @jhowardmsft to see if he has details

@jhowardmsft

This comment has been minimized.

jhowardmsft commented Nov 13, 2016

No, the ISE isn't fixed. AFAIK there's no intention of 'fixing' interactive in ISE as it's by design.

@rn

This comment has been minimized.

Contributor

rn commented Nov 13, 2016

@jhowardmsft thanks for the confirmation. Closing this as won't fix

@rn rn closed this Nov 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment