- Developers are seeking a reliable, secure system to build container images.
- Operators are looking for alternatives to managing and securing a separate build infrastructure.
The container ecosystem explosion began with developers running
docker build and
docker push on their local machines. But increasingly, developers have discovered the benefits of building container images remotely in the cloud, such as better automation, supply chain security, visibility and observability, increased efficiency from caching, and more.
With supply chain security becoming a hot topic in 2021, operators don't want to manage and secure a separate bespoke build infrastructure. In the past, this "build infrastructure" has sometimes been as simple as a shared computer running under a developer's desk. However, that build environment was difficult to manage, upgrade, and secure. Furthermore, often, it ran with very privileged access to production environments, making it a prime target for attackers.
Instead, operators want to lean on the tools and experience they've gained to secure and observe their production environments running on Kubernetes. Moving container image builds into the cluster is a natural fit, but running
docker build in a cluster can be very hard to secure properly.
Build container images with Shipwright
Shipwright is a modern, flexible, secure framework for building container images on a Kubernetes cluster, using familiar Kubernetes-style APIs, and running workloads using Tekton.
Shipwright lets you take advantage of an array of modern container build tools like Cloud Native Buildpacks, Kaniko, Buildah, Source-to-Image (S2I), BuildKit, and ko, and is flexible enough to quickly adapt to whatever new tools come along in the future.
Shipwright already powers IBM Cloud Code Engine's build system and will form the basis for Red Hat OpenShift builds version 2, which is expected to be launched in technical preview later this year. Shipwright is being proposed as an incubating project under the Continuous Delivery Foundation, a Linux Foundation initiative that provides a neutral home for modern continuous delivery projects of all kinds.
For more information about Shipwright, join us at cdCon on Wednesday, June 23, for Introduction to Shipwright, where I'll present an overview of the project, and on Thursday, June 24, for Project Shipwright in Depth, where Adam Kaplan and Enrique Encalada will go into more detail.
Until then, you can find documentation at https://shipwright.io and find the code on GitHub. You can also check out the article Project Shipwright and the future of Red Hat OpenShift builds on Red Hat Developer.