#Dockerd services issue

1 messages · Page 1 of 1 (latest)

placid comet
#

hrm, I busted the cache and ran the second function again (the one in the comment) now the output is as expected 🤔

#

And with the cache busted the original function still does not work. So it seems like a new service is created for each call, which kind of makes sense in the dag, but I expected the service to be reused

#

@jade roost this means your daggerverse/docker module does not work with the current release, which is how I got here 😅

jade roost
#

i think it already didn't work before... that behavior was already there. It only sort of worked because I had the docker state in a volume

#

and I agree it's a potential problem.

#

even if the current behavior is correct, we need to document it better

placid comet
jade roost
#

which I discovered when I tried to remove the cache volume...

placid comet
#

😅

#

so to rearchitect in the way the dag wants, we'd have to pass the dockerd service to each cli call function I guess

jade roost
#

I think I already do that

#

the engine is in the cli state