Erik Sipsma

> Eg. examples I posted above don't use cache mounts afaik. Bincastle's current approach doesn't involve cache mounts and should hopefully be formalized upstream once buildkit has support for [merge-op](https://github.com/moby/buildkit/issues/1431)...

@vito Thanks for the info! I am currently investigating adapting apk package DAGs to LLB using merge+diff, but doing the same investigation for nix is on my eventual TODO list,...

@tonistiigi > One approach might be to add packages on separate layers with a merge and then one layer on top of it with apk/world etc for all the packages....

@nlewo Thanks for the info! I have some extra thoughts on how nix2container could integrate with buildkit, but please don't let this stop you from contributing to `buildkit-nix` right away...

@shykes Yes good call, #4217 is the more "modern" 0.3 incantation of the same underlying issue, makes sense to track there now. Closing this one

If this is indeed the grpc issue, then that was fixed in this PR: https://github.com/moby/buildkit/pull/3940 So worth a try to see if fixed in v0.12

> This is still an issue with 0.12 + buildx at least. Sad, but now that I think about it again, I guess that PR only applied a fix to...

> appear in a GitHub action and the job continued. That's different than the problem in the issue description. Network errors are now non-fatal when you are either exporting cache...

> I would suggest to not remove the feature flag for now: Sounds good! It'll be easy to make this toggle-able still. And honestly even in the long run it...

> This potentially has quite a lot of implications for buildkit. Agreed, I think the baseline for all the impacted buildkit features would be to just disable the optimizations when...