Container stderr on error | Dagger | Page 1

regal hollow Jan 5, 2023, 8:22 PM

#

I think that is a known bug, let me try and find the issue

#

This seems to be it, but it's closed? https://github.com/dagger/dagger/issues/3025

GitHub

Include output of failed exec in graphql errors · Issue #3025 · dag...

Right now if an exec fails the graphql error just says that it exited non-zero. This makes it hard to debug unless you go look at the buildkit progress output. We should instead include the output ...

#

@inland abyss are you using the latest version of the Go SDK? I'm wondering if perhaps it has been fixed in a more recent release

kindred sundial Jan 5, 2023, 8:33 PM

#

Mentioned in the linked issue too, but this has been fixed but not released yet. We should be making the new release in the very near future, next Monday at the latest. After that you can upgrade and the stderr of your process will be included in the returned error message when it exits non-zero

inland abyss Jan 6, 2023, 8:23 AM

#

regal hollow <@775685040109256726> are you using the latest version of the Go SDK? I'm wonder...

Described issue was reproduced on the latest version of Go SDK: dagger.io/dagger v0.4.2

inland abyss Jan 10, 2023, 7:15 PM

#

kindred sundial Mentioned in the linked issue too, but this has been fixed but not released yet....

I’ve upgraded to 0.4.3 , and it works correctly now.!

#Container stderr on error