Skip to content
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

Dashboard "exec" should run cmd.exe on Windows pods instead of bash #2888

Closed
feiskyer opened this issue Mar 12, 2018 · 5 comments
Closed

Dashboard "exec" should run cmd.exe on Windows pods instead of bash #2888

feiskyer opened this issue Mar 12, 2018 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/windows Categorizes an issue or PR as relevant to SIG Windows.

Comments

@feiskyer
Copy link
Member

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

How to reproduce it (as minimally and precisely as possible):

  1. Deploy a Kubernetes cluster with Windows nodes
  2. Deploy any Windows pod
  3. Go to Kubernetes dashboard, find the pod, and click "exec" at the top

What happened:

This tried to launch bash which isn't on Windows by default.

container dd24fce994bbab4b0376b723e76f1257129492a8829d404d5913cd707bab3868 encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2) extra info: {"ApplicationName":"","CommandLine":"bash","User":"","WorkingDirectory":"C:\\","Environment":{"IIS_PORT":"tcp://10.0.132.120:80","IIS_PORT_80_TCP":"tcp://10.0.132.120:80","IIS_PORT_80_TCP_ADDR":"10.0.132.120","IIS_PORT_80_TCP_PORT":"80","IIS_PORT_80_TCP_PROTO":"tcp","IIS_SERVICE_HOST":"10.0.132.120","IIS_SERVICE_PORT":"80","IIS_SERVICE_PORT_TCP_80_80_VSRHX":"80","KUBERNETES_PORT":"tcp://10.0.0.1:443","KUBERNETES_PORT_443_TCP":"tcp://10.0.0.1:443","KUBERNETES_PORT_443_TCP_ADDR":"10.0.0.1","KUBERNETES_PORT_443_TCP_PORT":"443","KUBERNETES_PORT_443_TCP_PROTO":"tcp","KUBERNETES_SERVICE_HOST":"10.0.0.1","KUBERNETES_SERVICE_PORT":"443","KUBERNETES_SERVICE_PORT_HTTPS":"443"},"EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"CreateStdErrPipe":false,"ConsoleSize":[0,0]}
container dd24fce994bbab4b0376b723e76f1257129492a8829d404d5913cd707bab3868 encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2) extra info: {"ApplicationName":"","CommandLine":"sh","User":"","WorkingDirectory":"C:\\","Environment":{"IIS_PORT":"tcp://10.0.132.120:80","IIS_PORT_80_TCP":"tcp://10.0.132.120:80","IIS_PORT_80_TCP_ADDR":"10.0.132.120","IIS_PORT_80_TCP_PORT":"80","IIS_PORT_80_TCP_PROTO":"tcp","IIS_SERVICE_HOST":"10.0.132.120","IIS_SERVICE_PORT":"80","IIS_SERVICE_PORT_TCP_80_80_VSRHX":"80","KUBERNETES_PORT":"tcp://10.0.0.1:443","KUBERNETES_PORT_443_TCP":"tcp://10.0.0.1:443","KUBERNETES_PORT_443_TCP_ADDR":"10.0.0.1","KUBERNETES_PORT_443_TCP_PORT":"443","KUBERNETES_PORT_443_TCP_PROTO":"tcp","KUBERNETES_SERVICE_HOST":"10.0.0.1","KUBERNETES_SERVICE_PORT":"443","KUBERNETES_SERVICE_PORT_HTTPS":"443"},"EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"CreateStdErrPipe":false,"ConsoleSize":[0,0]}

What you expected to happen:

On Windows, it should default to running cmd.exe instead. Probably add cmd.exe here https://github.com/kubernetes/dashboard/blob/master/src/app/backend/handler/terminal.go#L257

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.9.3
  • Cloud provider or hardware configuration: Azure steps
  • OS (e.g. from /etc/os-release): Windows Server, version 1709

Labels
/sig windows

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. sig/windows Categorizes an issue or PR as relevant to SIG Windows. labels Mar 12, 2018
@feiskyer
Copy link
Member Author

/cc @PatrickLang

@floreks
Copy link
Member

floreks commented Mar 12, 2018

Closing in favor of #2029. All enhancements are tracked from there.

@floreks floreks closed this as completed Mar 12, 2018
@PatrickLang
Copy link

So will there be multiple PRs tracked against #2029, or is there one big PR that someone is already working on?

@floreks
Copy link
Member

floreks commented Mar 12, 2018

There should be multiple PRs related to #2029. I don't think that anyone is working on it currently.

@feiskyer
Copy link
Member Author

Filed a PR #2922 to fix this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/windows Categorizes an issue or PR as relevant to SIG Windows.
Projects
None yet
Development

No branches or pull requests

4 participants