#It seems like dagger is not cleaning up
1 messages · Page 1 of 1 (latest)
Also is /_shim handling SIGCHLD?
Not killing build makes run->cancel->update->run fail until the command finally exits.
(or at least it can depending on things... such as sharing apt cache locks)
Don't think so - that sounds like a good idea to me
Not sure what you mean here, sorry
Do you mean it's possible to leak a zombie process that's holding a flock since it's never reaped?
Not even just not reaped, I mean the process is still running even though my client is gone.
oh, what Dagger version?
go-sdk is v0.5.2
Engine is at registry.dagger.io/engine:v0.4.2
ah, yeah that was a known issue in engine v0.4.2
it's fixed in v0.5.0 - root cause was https://github.com/moby/buildkit/issues/3751