Eric Hripko

> The idea of needing a Dockerfile to execute buildpacks which in most cases would only require one option (the builder) seems like a poor experience. Definitely agree on this...

IIUC, it's fairly straightforward as you get final values of build args as `map[string]string`. I've jotted down a barebones implementation of this in my repo (see https://github.com/EricHripko/cnbp/commit/32bb24b6686d2baa247627698ac397177dad108c). Setting `--build-arg BP_JVM_VERSION=8`...

Another quick update: I had a go at implementing caching with BuildKit build-time mounts. It somewhat works with a bunch of caveats (see https://github.com/EricHripko/cnbp/commit/96e4d774d8b601cf46f66f3830cfa03279f07ced); key takeaways for me were: -...

Hi @jromero - thank you for this invitation! I've emailed you to understand this a bit more 🙂

Thank you for sharing the recoding and thanks to community for having me 🙂 At the very least, `llb.Copy` supports [AttemptUnpack](https://github.com/moby/buildkit/blob/4e69662758446c7dc0e6de2bc1f7973d03bacbed/client/llb/fileop.go#L430) flag which should be able to take a tarball...

Facing the same issue as what @astorath described - we have an `ONBUILD` build and `ONBUILD` runtime stages to streamline the `Dockerfile`s. Lack of this feature in `buildkit` is big...

Hey folks 👋 Docker Desktop 2.4.0.0 enables BuildKit by default now, which will potentially break any `Dockerfile`s dependent on this functionality. I'm happy to work with maintainers to get this...

> If you are hitting this I strongly also advise you to look if this is actually a correct solution for your problem I think this solution is born out...

I've written up a [blog post](https://medium.com/@eric.hripko/3-ways-to-streamline-your-container-images-with-buildkit-7a5a4c8638b7) to document some alternatives to `ONBUILD COPY --from`. These vary in flexibility (and, as a result, complexity) but are all compatible with BuildKit 🎉...

Hi @chrmarti! Thank you for the update on this 👍 We tried it out and the issue seems to still be occurring on `0.258.0`: ``` [1826 ms] TypeError: Cannot read...