Erik Sipsma

@nipuna-perera @vito @jedevc updated the PR description with a new iteration on the proposed fixes. It's cobbled together from the previous one and other comments, so apologies for anything you've...

Just FYI for everyone following this issue, I updated the description of the issue with the current state of support and what's planned for the future. These features are still...

@OptikMist > ✘ Container.from(address: ""): Container! 0.0s Just double checking, did you leave out the name of the image for privacy reasons? Or did it actually show up as `address:...

> If we think this is safe(for buildkit's use-cases) then we should add it to all our overlay mounts, not only with containerd worker, and not requiring custom config from...

What command were you running that hit the `toolchain not available` error? I've been running today on top of that change without any issues, so just curious how this gets...

> > would be nice to update our CI here too to call this new functionality and output the pprof profiles as GHA artifacts. I _think_ that's relatively straightforward, but...

> @sipsma, if I do a second _resolve from caller_, _initialize_, etc... with an open session, does it do anything? I mean, do changed files get picked up? IIUC it...

I wouldn't be opposed to a one-off "disable cache" option meant to be used purely for debugging. I'd probably want it hidden away but agree it's nice while debugging to...

> Failure on test everything else isn't related to this PR: https://v3.dagger.cloud/dagger/traces/e3aec1efb6618d36d5a2fe2b6807c641?listen=bdc294a9d8aa54cc&span=5cb3827b70f01851 The failure in there appears to be: ``` failed to get required client generation files: failed to get...

Trying it out locally, super cool! One thing I noticed so far --- ``` go mod init dagger.io/demo dagger init dagger install github.com/shykes/hello cat >main.go