I have dagger-buildkitd lingering effectively forever after doing something with the Go SDK. Is this expected? Can I turn it off automatically somehow after dagger.Connect()?
#How to turn off dagger-buildkitd container automatically after using Go SDK?
little hinge
turbid kindle
I have dagger-buildkitd lingering effectively forever after doing something with...
Hi,
I don't think we handle that for now. The reason why is: whenever you run it once, it will cache all your steps, and the next iterations will benefit from the cache of the previous run. Without it, it wouldn't be possible. It is an interesting DX behavior though, related to the Dagger architecture: https://github.com/dagger/dagger/issues/3595. Feel free to create an issue explaining 1) the need + 2) the expected behavior 🙏