Skip to content
SPECIFICTION
Get listed

Paketo Buildpacks vs Source-to-Image

Paketo Buildpacks

paketo.io

Source-to-Image

github.com

Side by side

FigurePaketo BuildpacksSource-to-Image
Price fromFreeFree
Free planYesYes
Free trial——
Open source—Yes
Windows—Yes
macOS—Yes
LinuxYesYes
Self-hostedYesYes
Plans published11
Spec score · Container Build Tools7.4 (#24)8.1 (#12)
IntegrationsThe site lists Docker and Kubernetes, CircleCI, GitLab, Tekton, HashiCorp Waypoint, the Pack CLI, Spring Boot, Tilt, and VMware Tanzu Build Service among compatible platforms and tools.The README documents use with Docker and gives examples using OpenShift, UBI, Ruby, and WildFly images.
PurposePaketo Buildpacks transform application source code into container images and provide production-ready buildpacks for popular languages and frameworks.Source-to-Image is a toolkit and workflow for building reproducible container images from source code.
SecurityPaketo stacks run as a dedicated non-root user when building and running applications.The project says S2I can control builder image permissions and privileges, and that OpenShift can help admins control developer build-time privileges.

Plans

Paketo Buildpacks

  • Paketo BuildpacksFree

Paketo Buildpacks pricing →

Source-to-Image

  • Source-to-ImageFree

Source-to-Image pricing →

In their own words

Paketo Buildpacks

Paketo Buildpacks has no write-up on Specifiction yet; its figures are above.

Visit paketo.io

Source-to-Image

Source-to-Image is a free, Apache-2.0 toolkit for building reproducible container images from source code. It places source in a builder image, lets that container prepare the application, and outputs a ready-to-run image. A documented workflow can build from a Git repository without a Dockerfile. Builder images may provide assemble and run scripts, plus optional scripts for saving artifacts and explaining usage. Compatible builders can reuse artifacts from an earlier output when incremental settings and scripts are supplied. A .s2iignore file filters source files and directories, while .s2i/environment defines build variables that also appear in the output image. S2I can use an OnBuild strategy with images containing Dockerfile ONBUILD instructions. Examples cover Docker, OpenShift, UBI, Ruby, and WildFly. It runs on Linux, macOS, and Windows, with Docker 1.6+ and Go 1.7.1+ listed as dependencies.

Visit github.com