Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Containers: PSSTYLE is a royal pain. Can we use environment variables for configuration? #14964

Copy link
Copy link
@Jaykul

Description

@Jaykul
Issue body actions

We really need a way to control PowerShell's configuration from outside a container.

Really, PowerShell should obviously respect ENVIRONMENT variables like TERM=dumb or NO_COLOR that we can set globally, and which we can pass into a docker container.

It needs to be something I can set when I'm not calling PowerShell directly, and ideally which works with existing containers, so I don't have to try to mount a system profile.ps1 into every different container we use...

Right now I have a docker container where PowerShell is being run with -NonInteractive but whenever there's an error it spews a bunch of [96m and [91m and so on...

image

While we're talking about it, I also want to turn off Progress output with an environment variable too, because the output in that screenshot is really weird.

Having to reach into a docker container and create a global profile to disable color isn't really a good solution.

Reactions are currently unavailable

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.