Using this exemple.
It takes so much time to initialize a tunnel (still idle after minutes)
https://docs.dagger.io/api/services/
What could I do to see why it is like this ? May be my local configuration ?
#Crazy startup time for service (hello world exemple)
junior lark
pulsar crane
Using this exemple.
It takes so much time to initialize a tunnel (still idle af...
👋 by any chance do you have a Dagger Cloud trace?
pulsar crane
@junior lark when you call dagger call http-service up from the example you provided above, that command is never supposed to finish
that will be running indefinitely as what it does is start the service and map the ports to your local machine so you can do curl localhost:8080
everything seems to be running ok in your case
it's similar as doing docker compose $myservice up
junior lark
ubuntu 22 last version of dagger
pulsar crane
ubuntu 22 last version of dagger
do you see this message when you call dagger call http-service up?
the tunnel started one
junior lark
no I don't see it.
I see it with your nginx module exemple
and netstat -tuln | grep 8080 gives nothing
pulsar crane
and ` netstat -tuln | grep 8080` gives nothing
can you run dagger call -vvv http-service up ?
do you get to see the exec python?
junior lark
nothing like this
pulsar crane
nothing like this
can you call dagger core engine local-cache prune and try again please?
wondering if it might be a caching thing.
it's strange that nginx is working but this example doesn't
junior lark
Yeah. I know... is it a different logic a module or ?
@pulsar crane I try in a fresh helloDagger install. And it works (engine v0.12.5)
I don't know what I can share to understand the differences
pulsar crane
@junior lark you were trying on v0.15.1 before?
are you sure that both the CLI and the Engine were using the same version?
junior lark
dagger verions : dagger v0.15.1 (registry.dagger.io/engine:v0.15.1) linux/amd64
docker container ls:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
51331211a1e3 registry.dagger.io/engine:v0.15.1 "dagger-entrypoint.s…" About an hour ago Up About an hour dagger-engine-v0.15.1
yep, that seems right. Mind jumping briefly to #911305510882513037 to check it together?
can you hear me @junior lark ?
I can hear you @junior lark
raw elk
do you have both turned on?
raw elk
volume up?
junior lark
I hear you now
pulsar crane
seems like the docs have been updated ineeded, they just haven't been published https://github.com/dagger/dagger/blob/main/docs/current_docs/api/snippets/services/bind-services/python/main.py#L16
cc @knotty skiff
pulsar crane
cc <@1013436980249505882>
strange that I also don't see in https://devel.docs.dagger.io/api/services/ even though it's merged to main
has the devel autopublish stopped working?
knotty skiff
Afaik the docs were republished with the release
I'll look into it shortly. I'm not sure why it's not showing up. @halcyon compass any ideas?
halcyon compass
Hm I think it's back now
Oh wait no
I remember we needed to purge the cache at some point?
trying that now
weird, because it's picked up the go changes fine
yeah that's done it i think
will do the same for the main docs
fixed on main docs now as well
pulsar crane
🙏 thx Justin