HostDirectory.write(DirectoryID) vs Directory.write(HostDirectoryID)

[coarse jetty]

🧵

one thing this surfaced is it's awkward to pass a HostDirectoryID for the workdir, because it's actually just a const "__dagger_workdir", not currently exposed

[unborn fjord]

@coarse jetty do we have a stable API for writing any directory to the host?

[coarse jetty]

HostDirectory.write exists, yeah, I don't know if it's "stable" though 😆

[unborn fjord]

Seems like if we have that, we should be able to compose it Container { rootfs } ?

oh no, nevermind

[coarse jetty]

it has to either be the workdir or a pre-configured host dir

[unborn fjord]

it's the OCI tarball forget I said anything

[coarse jetty]

right right, I need a proper OCI image with config and all that jazz

[unborn fjord]

OK I have what I need to compose an appropriately bikesheddy response

[coarse jetty]

excellent

[unborn fjord]

and done

[compact warren]

We used a trick with FSID where "scratch" was a special scalar value that indicated scratch. I have a memory of us doing the same thing with host workdir, but I could be making it up

[compact warren]

But also relevent to that, as part of the dagger.json stuff that __dagger_workdir is no longer a const, it gets changed in each buildkit session (to fix some other issues)

[coarse jetty]

I like the idea of leveraging Directory, I think it might be hard to put the export back into an LLB representation though 🤔 ... unless we overload Directory and make that happen late?

[coarse jetty]

oh awesome, i was thinking about doing that