More room to run
Up until now, every step in 3B was built from an image called 3b/base, an image we curated with a few languages and tools already in it, and 3B built those steps with its own builder. As users build more on 3B, they want their own OS, custom operating system packages, and often the base images their security team has already approved. It was only a matter of time before we supported it at scale. And today, I am very excited to share that each step in 3B can use any Dockerfile. Your step can run python, rust, node, or whatever image you already use, and it works the same way it does on your laptop.
We obsess about performance at 3B, and we knew that building and running containers with custom images would bring many interesting infrastructure and distributed systems challenges, which made it quite fun to work on.
For example, we split each image into small pieces (chunks), and a step only fetches the pieces it actually reads. This, alongside a few other architectural and Linux “tricks” (dare I say), is how we can build and start a fresh sandbox for every step quickly and at scale. We will have more to share about the internals soon.
3B also supports private images for your steps. If your team keeps its own base images in a private registry, a step can now start from one of them once you add a Docker Hub, Amazon ECR, or Chainguard connector. When the build asks the registry for access, 3B adds your credentials the same way it does for connectors when a step runs, so your token never ends up inside the build.
I can’t wait to see what you build next 🚀