Skip to content
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.

PowerShell (5.1) (Windows) Container #596

Closed
kilasuit opened this issue Oct 4, 2020 · 3 comments
Closed

PowerShell (5.1) (Windows) Container #596

kilasuit opened this issue Oct 4, 2020 · 3 comments
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@kilasuit
Copy link

kilasuit commented Oct 4, 2020

Add a Windows based devcontainer for older PowerShell development needs where developing for PowerShell 7 isn't possible

@Chuxel Chuxel added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Oct 6, 2020
@Chuxel
Copy link
Member

Chuxel commented Oct 6, 2020

Thanks for the issue! Unfortunately, there isn't a PowerShell container image for versions earlier than 6. We also don't currently support windows containers (see microsoft/vscode-remote-release#445). As a result, I don't know that we'll really be able to do this realistically. I'm going to close this as "upstream" since both of these would need to change before we could pick anything up.

@Chuxel Chuxel closed this as completed Oct 6, 2020
@kilasuit
Copy link
Author

kilasuit commented Oct 7, 2020

@Chuxel actually there is - it would need to use the WindowsServerCore image & would only be usable on windows machines

I am happy to add in a container for this (& add that it will be Windows only) but wanted to see if this would be accepted before spending too much time on it?

The key scenario would not be for use in codespaces but local remote development containers.

@Chuxel
Copy link
Member

Chuxel commented Oct 7, 2020

@kilasuit Yeah, Remote - Containers (local) doesn't support WindowsServerCore images (that's microsoft/vscode-remote-release#445 above). It fires shell commands to do what it needs to do to get up and running, so I'd expect it to fail. LCOW also had issues due to missing features at the time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants