Issue during deployments with output streams on PowerShell scripts inside Linux docker containers
Severity
No response
Version
+/-2024.2.6366
Latest Version
I could reproduce the problem in the latest build
What happened?
Diagnostic outputs sent to std-err from other tools (such as docker run) cause Octopus to log these as errors.
Service messages can be used as workarounds however this suppresses actual errors - which hinders debugging when things go wrong.
You could use Write-Error to override that function however this only works for scenarios where errors have been explicitly caught and directed to Write-Error.
Ideally looking for a better way to handle these scenarios in a more graceful manner.
Reproduction
This can be seen when running docker run inside Octopus with the Hello World container, information is logged to std-err which may cause issues/confusion when inspecting logs.
Error and Stacktrace
No response
More Information
No response
Workaround
No response
Excellent in-depth explanation on this user ticket: https://octopus.zendesk.com/agent/tickets/183905
Release Note: Added new service message ##octopus[stderr-output] to print stderr logs as info logs
:tada: The fix for this issue has been released in:
| Release stream | Release |
|---|---|
| 2025.3 | 2025.3.770 |
| 2025.4+ | all releases |