service.wait | Dagger | Page 1

forest obsidian Mar 3, 2026, 7:34 PM

#

there is an existing wait function under https://github.com/alexcb/dagger/blob/d19c8bb01d5380e7d11e5206520731d1ead0c6b7/core/service.go#L684

it would think it would be possible to plumb it through (in the same way that stop is plumbed through).

#

(just updated the link, I had the wrong line initially)

#

there's also a similar Exec: execSvc, function that's stored which could do the exec.

#

I'm curious what your use case is

mystic walrus Mar 3, 2026, 7:49 PM

#

Same thing as in this thread: https://discord.com/channels/707636530424053791/1465802018663698627

tl;dr implementing the Docker API with Dagger as the runtime

forest obsidian Mar 3, 2026, 8:11 PM

#

there's an old issue under https://github.com/dagger/dagger/issues/6553 which seems similar?

GitHub

✨ Access Service stdout/stderr and exit code · Issue #6553 · da...

What are you trying to do? Currently, once a service starts, there's not a ton of interaction points for it. We can stop it... and that's about it. One key thing I'd like is access to t...

mystic walrus Mar 3, 2026, 8:12 PM

#

yeah, that's super related. I've got the stdout/stderr bit roughly handled using OTEL at this point. As is mentioned in that issue, I think that plumbing stdout/stderr streams from Dagger would be difficult, hence why I opted to use OTEL instead of trying to build it into the Dagger API. The exit code bit should be much easier, I figured

#service.wait