Can't call Service.Sync() | Dagger | Page 1

nimble nova Oct 30, 2023, 7:54 PM

#

It looks like I can't call Service.Sync(). How do I block until a service is terminated?

#

Note: this is something I can do with Container

lusty oasis Oct 30, 2023, 7:58 PM

#

Are you looking for Service.Stop()? Or what is the goal?

nimble nova Oct 30, 2023, 10:23 PM

#

lusty oasis Are you looking for `Service.Stop()`? Or what is the goal?

Run the service, basically. I expect the call to never return (only be interrupted eventually when the user Ctrl-Cs)

#

Before 0.9., I achieved this with Container.Sync

potent finch Oct 30, 2023, 11:28 PM

#

I guess the equivalent is Start now?

#

Oh! Start doesn't wait for the service to finish. Yeah.. seems like a single call which starts the service and waits is not there in the service type

nimble nova Oct 30, 2023, 11:34 PM

#

I think that's actually OK (at least in Go), I can call Start() then block manually on the context

lusty oasis Oct 31, 2023, 12:01 AM

#

Since it's not listening on a port, would you still use Container.Sync and dagger call instead of Service/up?

nimble nova Oct 31, 2023, 12:02 AM

#

Maybe. I was wondering that.

#

But now that I got my function working with dagger up (by exposing a bogus port), it feels right to have it be a service

#

It does pose the question of what exactly is and isn't a service

#

If I had my function return a *Container instead, and made no other change, I would lose the ability to run that container from the CLI, since there is no dagger run that takes a function returning a container, and runs that container

#

Ie:

dagger up -m github.com/shykes/daggerverse/tailscale gateway --> this works right now 🙂
dagger call -m github.com/shykes/daggerverse/tailscale gateway -> this wouldn't do anything, I think

#

Maybe dagger up should support Container in addition to Service, and just run the container as is?

#Can't call Service.Sync()