4 ms·
> We believe that today we are the only hosted CI or build service offering the ability to natively build multi-platform Docker images Dagger.io, by the origin
by verdverm 4y ago
> We believe that today we are the only hosted CI or build service offering the ability to natively build multi-platform Docker images
Dagger.io, by the originators of docker, can do this too, though it is not well documented. They have not yet enable public signups either by the looks of it.
Pretty sure I've seen some other BuildKit frontends that do as well, the space blew up this year with several startups
- jacobwg 4y agoI haven't had a chance to experiment with it yet, but it should be possible to run Dagger pipelines on Depot builders. Depot is effectively a BuildKit-API-as-a-service currently, and Dagger can connect to an external BuildKit host (https://docs.dagger.io/1223/custom-buildkit/ https://docs.dagger.io/1223/custom-buildkit/). It would be cool to add an integration between Depot's CLI and Dagger's CLI such that Dagger could communicate with the remote builder machine. You could use Dagger with remote compute without needing to manage that compute, effectively. Depot even supports launching builders within your own AWS account, so you'd have that same ability with Dagger as well.
- mdaniel 4y agoDagger is Apache 2, no signup required: https://github.com/dagger/dagger#readme https://github.com/dagger/dagger#readme I struggle to think of what I would need a SaaS service to run BuildKit for me unless they're trying to take on GitHub Actions's compute side or whatever
- jacobwg 4y agoI think we are trying to take on GitHub Actions' compute side yeah — you'd want to either self-host your own BuildKit or use something like Depot for two major reasons: 1. Several of BuildKit's caching features either require or work best with a local disk. For instance things like `RUN --mount=type=cache` need a persistent disk, which Actions doesn't provide. You can also hit bottlenecks with saving and loading tarball cache from Actions (e.g. cache-from / cache-to) where it takes longer to download and unpack the tarballs compared to omitting the cache. Having a persistent disk makes all this "instant". 2. If you need to build images for ARM CPUs, QEMU in GitHub Actions is really slow. And if you want to build multi-platform images natively (e.g. --platform linux/amd64,linux/arm64), BuildKit needs a simultaneous connection to two native builders. Depot automates all that (it will launch two VMs at once and connect them to the build). GitHub Actions today also only offers 2 CPUs for the build - they're launching a beta of larger machine sizes currently.
- verdverm 4y agoDagger is helping companies scale BuildKit in a self-hosted setup (that I am aware of). Not sure about the Dagger + GHA self-hosted runner story, one would assume it would be a natural extension of their general self-hosted BuildKit, just point Dagger at whatever BuildKit domain/ip you are using. Dagger is open-source, but also has paid things if you talk to them. They are very focused on a few key users in their paid plans, rather than opening the floodgates, as I understand it.