```

[final vessel]

👋 any chance you can share a Dagger Cloud trace URL?

if you do dagger login in the CLI that will get you a Dagger Cloud account

[valid jungle]

hmm, I didn't have a trace, as i wasn't logged in; figured the issue out another way; the nginx container was starting itself as a demon in the background so it looked like it exited too early.

dagger needs a bit of a better way to debug errant services though

[final vessel]

I you call dagger with -vvv and -E that will allow you to navigate the TUI output even after dagger has existed. I usually do that to troubleshoot misbehaving services

having said this, these kind of errors are better observed in the Cloud UI

as we have a more rich set of UI elements to specifically pin-point where things are not working

would love to get some feedback if you manage to try it out

[valid jungle]

-E was probably what I was missing. Will give that a go next time I run into an issue