#@solomon what if we made a cache key per
viscid edge
creating 🧵
having multiple jobs per PR is quite common, if you're in this situation, that won't work
also persisting the /var/lib/dagger in Github's cache will be extremely slow and inefficient .
you can go ahead and try it out but I've been down that road before and it's pretty much a dead end. There's also a reason why Docker also doesn't recommend that (https://docs.docker.com/build/cache/backends/gha/).
FWIW Dagger can also work with the same GHA exporter. As mentioned and shared in the buildkit link before, GHA is generally quite unstable when using it for container layer caching. Hopefully it works for your use case, but I haven't had much success with it in the past.
fervent spire
I'm not talking about docker caching
I'm talking about artifact caching (for volumes)
So can we persist a docker volume content as a .tgz rather than caching the docker layer itself?
So you're just snapshotting a DIR to .tgz and unpacking into a dir
viscid edge
ok, @glass cloak question was about /var/lib/dagger that's the context of my reply. Volume caching is a different story
there's no way of doing that currently without migrating the whole state of the engine
Dagger doesn't have a way to export / import volumes
fervent spire
Okay. Is it possible with export() to dump out a directory and it's contents ? @viscid edge at the moment
viscid edge
Okay. Is it possible with export() to dump out a directory and it's contents ? <...
yes, if you're intending to export cache volumes, you'll have to manually copy those to an empty container first since you can't export directories from cache volumes directly. i.e: dagger --no-mod -c 'container | from alpine | with-mounted-cache /foo $(cache-volume foo) | with-exec sh,-c,"echo hello > /foo/hello.txt" | with-exec cp,-r,/foo,/export | directory /export | export ./out'
fervent spire
do we yet have a thingy that can convert dagger shell into code?
maybe dagger shell -> graphql -> code gen?
that'd be a neat tool
viscid edge
that'd be a neat tool
we have dagger llm for that 😄
fervent spire
can you paste in shell commands into dagger llm ?
viscid edge
I mean... you can ask dagger llm to translate the code for you
fervent spire
oh? it understands dagger shell?
viscid edge
you might have to give it a bit of dagger code so it generalizes the best way possible
viscid edge
oh? it understands dagger shell?
no, but it should be relatively easy to teach it
with a prompt
fervent spire
ok, so not yet, just checking 🙂
was talking to Solomon about it on twitter, and Kyle posting something (dagger llm -> codegen)