Not all commands seem to respect the Quiet switch.
E.g. Invoke-DockerPull seems not to pass the Quiet switch to the Invoke-DockerCommand.
Also the docker process output is written using Write-Information -InformationAction 'Continue', which means, that the caller can't properly control the information stream. E.g. using Invoke-DockerPull -InformationAction Ignore will not work as expected (the information output will still be produced).
This means, that the only way of not having the Invoke-DockerCommand produce any output to the information channel, is by using the DOCKER_CI_QUIET_MODE environment variable, which is not very convenient, when you're writing a more complex automation/script where some output should be produced and some not.
Not all commands seem to respect the
Quietswitch. E.g.Invoke-DockerPullseems not to pass theQuietswitch to theInvoke-DockerCommand. Also the docker process output is written usingWrite-Information -InformationAction 'Continue', which means, that the caller can't properly control the information stream. E.g. usingInvoke-DockerPull -InformationAction Ignorewill not work as expected (the information output will still be produced). This means, that the only way of not having theInvoke-DockerCommandproduce any output to the information channel, is by using the DOCKER_CI_QUIET_MODE environment variable, which is not very convenient, when you're writing a more complex automation/script where some output should be produced and some not.