Warn when az container exec with --os-type windows

[davetapley]

Is your feature request related to a problem? Please describe.

If I try to run Powershell in a container like this ⬇️ it just exits immediately with no feedback.

$ az container create --os-type windows --resource-group dev --name win-sandbox --image mcr.microsoft.com/windows/servercore:1809
$ az container exec -g dev --name win-sandbox --exec-command "powershell.exe" 
$ # back at prompt immediately with no feedback

This is hidden in the docs ⬇️, but it took a StackOverflow question to lead me there.

This command is currently not supported for Windows machines.

Describe the solution you'd like

Ideally it would Just Work, but assuming that's not coming soon, then a warning / explanation of what happened would be nice.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @macolso.

Issue Details

---

Is your feature request related to a problem? Please describe.

If I try to run Powershell in a container like this ⬇️ it just exits immediately with no feedback.

$ az container create --os-type windows --resource-group dev --name win-sandbox --image mcr.microsoft.com/windows/servercore:1809
$ az container exec -g dev --name win-sandbox --exec-command "powershell.exe" 
$ # back at prompt immediately with no feedback

This is hidden in the docs ⬇️, but it took a StackOverflow question to lead me there.

This command is currently not supported for Windows machines.

Describe the solution you'd like

Ideally it would Just Work, but assuming that's not coming soon, then a warning / explanation of what happened would be nice.

Author:	davetapley
Assignees:	-
Labels:	Service Attention, Container Instances, customer-reported
Milestone:	-

[yonzhan]

route to service team

[davetapley]

I did a bit more digging and found these docs which suggest interactive should work.
The cmd.exe example in there was added in March 2018: MicrosoftDocs/azure-docs@2e39460

But the ⬇️ comment I noted originally is from Sept 2019.

This command is currently not supported for Windows machines.

Makes me wonder if interactive did work at some point but has since become unsupported?
If so that seems like big regression 😑