David Boreham

After a bit of running the cabal 'new-install' command with `strace`, I'm wondering if my problem is something to do with a package cache cabal is referencing. I see it...

> As of [v23.0.0](https://github.com/moby/moby/releases/tag/v23.0.0) BuildKit is the default builder on Linux. Is there a good way to disable it (since it's not compatible with all existing use cases) through the...

> > As of [v23.0.0](https://github.com/moby/moby/releases/tag/v23.0.0) BuildKit is the default builder on Linux. > > Is there a good way to disable it (since it's not compatible with all existing use...

> > everything breaks due to buildkit being enabled as the default > > @dboreham Would you mind posting a repro with a Dockerfile and build command so we can...

fwiw I have also had problems in the past with BuildKit on ARM, I think to do with the container images it depends on (BuildKit's images) not published for that...

> Agreed @bryanhuntesl What did you end up doing for this? So no way to have custom networks and docker secrets throughout build time. Also no way to have build...

Also landed here after failing to see how to add a user to an org. Even after reading this issue 6 times it was still not obvious how to do...

> ... let alone adding container nesting on Windows. Quick note for the audience with no Windows exposure: containers/docker on Windows (except for actual Windows containers which nobody uses) runs...

init is out of scope here though, since we're running inside a container. btw it turns out nested kind works just fine now, provided the container has the necessary secret...

Well, I've tested stock WSL2 on x86 and it works. I'll try aarm64 and report back...