Joel Longtine

> Firstly, here is a rewritten version of @jlongtine's repro (the original didn't run for me). Joel, perhaps you can confirm this is faithful to your original? Quick pass looks...

@helderco Just dropping a note to say that I'd love to have this pattern in my refactor of `internal/mage`. There are a few bits of code that would be much...

> Awesome! Is this something we should plan to release, or the first in a series of PRs to get us to a releaseable state? That's an open question for...

I had a good discussion today with @sipsma and @vito about this. Our proposal as a first pass (with subsequent designs for extensions, etc) is to add a GraphQL API...

A couple of things to note: `func (r *Container) WithWorkdir(path string) *Container` [already exists](https://github.com/dagger/dagger-go-sdk/blob/main/api.gen.go#L503), `func (r *Container) Workdir(ctx context.Context) (string, error)` is for retrieving the currently set `Workdir`. I can...

> Have you ever had the need to actually pass some `io.Writer` to it? Or it was always small enough that some `[]byte` or `string` was enough? Given that it's...

> Correct. `WithNewFile` is limited to small files because it ends up as a single gRPC call to buildkit (not a streaming thing). If it's above a few kilobytes it...

I'd suggest we implement permissions in these APIs: ```graphqls type Directory { withFile(path: String!, source: FileID!, permissions: Int): Directory! withNewFile(path: String!, contents: String!, permissions: Int): Directory! withDirectory( path: String! directory:...

> Regarding host-to-service (**IF** it's always a service), then we can have some service specific instructions: I like option 1, personally. Keeps it in code, keeps it at service "boot"....

> @jlongtine Good question - I think we likely won't ever need to call 'expose' for container-to-container (within Buildkit network). So I think we can get away with having `Expose`...