You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
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.
We really need a way to control PowerShell's configuration from outside a container.
Really, PowerShell should obviously respect ENVIRONMENT variables like
TERM=dumborNO_COLORthat 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.ps1into every different container we use...Right now I have a docker container where PowerShell is being run with
-NonInteractivebut whenever there's an error it spews a bunch of[96mand[91mand so on...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.