Displaying logs from when calling external commands from a powershell script

Question

In a powershell module there is a class with the following method (here simplified). It simply calls docker to automatically build an image.

Everything works and the image is correctly built. What I cannot understand is why the logs from docker are not printed in the console (as they do if I call the same docker command directly instead of inside a powershell module).

[void] BuildImage() {
    $imageId = ...
    docker build -f ../Dockerfile . -t $imageId
}

if the docker command is an external command a & at the start would be correct in anyway, even if it is not the root cause of the problem. & docker build -f ../Dockerfile . -t $imageId — Carsten.R
– Carsten.R, Commented May 5, 2023 at 3:52

Santiago Squarzon · Accepted Answer · 2023-05-05 04:04:23Z

1

You have a void method, it produces no output. If you want to send output to the success stream (stdout), then change the return type to [string[]] and use return:

[string[]] BuildImage() {
    $imageId = ...
    return docker build -f ../Dockerfile . -t $imageId
}

If instead you're interested in sending the output to the other PowerShell streams, you could try the following example which includes redirection of errors then checks if the output type was an ErrorRecord it sends it to the error stream otherwise it sends it to the information stream.

[void] BuildImage() {
    $imageId = ...
    docker build -f ../Dockerfile . -t $imageId 2>&1 | ForEach-Object {
        if($_ -is [System.Management.Automation.ErrorRecord]) {
            return Write-Error $_
        }

        Write-Host $_
    }
}

edited May 5, 2023 at 4:04

answered May 5, 2023 at 3:26

Santiago Squarzon

65.7k5 gold badges26 silver badges60 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Franco Tiveron Over a year ago

Unfortunately piping to Write-Host doesn't change the result

Santiago Squarzon Over a year ago

@FrancoTiveron try with that update, perhaps its sending output to the stderr, adding 2>&1 might solve the problem

Collectives™ on Stack Overflow

Displaying logs from when calling external commands from a powershell script

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related