Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Source-to-Image

github.com

  • Free plan
  • Open source
  • Windows
  • macOS
  • Linux
  • Self-hosted
7.9 Club score Visit github.com

What Source-to-Image is

Source-to-Image is a free, open-source toolkit for building reproducible container images from source code. It injects application source into a builder image, lets that container prepare the code for execution, and produces a ready-to-run image. The documented workflow can use a Git repository without a Dockerfile. Builder images may provide assemble and run scripts, plus optional scripts for saving artifacts and describing usage. With a compatible builder, a previous output image, a save-artifacts script and --incremental=true, S2I can reuse artifacts from an earlier build. A .s2iignore file filters source files and directories, while .s2i/environment supplies build variables that also appear in the output image. S2I recognizes Dockerfile ONBUILD instructions through an OnBuild strategy. Documentation includes Docker, OpenShift, UBI, Ruby and WildFly examples. The project is licensed Apache-2.0 and listed for Linux, macOS and Windows. Dependencies include Docker 1.6 or later and Go 1.7.1 or later; Git is optional. No paid plans are stated.

Who it suits

It suits developers building container images from source with builder images and scripted workflows. It is also useful for teams using Docker or OpenShift that want reproducible builds without requiring a Dockerfile.

Good to know, and what to watch

  • Builds reproducible images from source code
  • Can build from Git without a Dockerfile
  • Supports incremental artifact reuse
  • Filters files with .s2iignore
  • Free under Apache-2.0 licensing
  • Requires Docker 1.6 or later
  • Requires Go 1.7.1 or later
  • Incremental builds need compatible builder support
  • Docker group membership can grant root access

Source-to-Image

Free

Free plan

The verdict

Source-to-Image provides a scriptable route from source code to runnable container images. Its builder conventions, filtering and incremental options give teams control over how application code is assembled.

What the maker publishes

API and SDK surface
The published interface is a Go-based CLI with documented subcommands; the README does not describe a hosted HTTP API or official SDKs. source
Build customization
Builder images can supply assemble and run scripts, with optional save-artifacts and usage scripts. source
Builder customization
OpenShift documentation says teams can customize S2I builder images and wrap embedded scripts to add application-specific behavior. source
Builder scripts
Builder images use assemble and run scripts, with optional save-artifacts and usage scripts. source
Build inputs
s2i build accepts a source location, builder image and optional output tag, with flags for environment, users, scripts and destinations. source
CLI commands
The CLI documents create, build, rebuild, generate, usage, version and help commands. source
Company founding
Red Hat says it was founded in 1993. source
Company headquarters
Red Hat lists its headquarters address as 100 E. Davie Street, Raleigh, North Carolina 27601. source
Company legal name
Crunchbase identifies the maker as Red Hat Inc., an IBM subsidiary. source
Company ownership
Red Hat says it has been joined with IBM since 2019, while IBM's acquisition announcement says Red Hat would remain a distinct unit. source
Company size
LinkedIn lists Red Hat as having more than 10,001 employees and headquarters in Raleigh, North Carolina. source
Company workforce fact
Red Hat's company brief reports more than 19,000 employees across 100 locations in over 40 countries. source
Dependencies
The README lists Docker 1.6 or later and Go 1.7.1 or later as dependencies, with Git optional. source
Docker access warning
The security notes say Docker group membership effectively grants root access and recommend sudo on recent Fedora/RHEL systems as more auditable and secure. source
Dockerfile alternative
The README demonstrates building and running an image from a Git repository without a Dockerfile. source
Dockerfile-free builds
The project can build an application image directly from a Git repository without requiring a Dockerfile. source
Docker integration
The documented default Docker socket is unix:///var/run/docker.sock, and S2I uses Docker client functionality for builds. source
Environment variables
Applications can define build environment variables in a .s2i/environment file, and those variables are also present in the output image. source
Environment variables
Values in .s2i/environment are passed into the build and remain available in the resulting application image. source
How it works
It injects source code into a builder container image, lets the container prepare the source for execution, and produces a ready-to-run image. source
Image support
S2I recognizes container images with Dockerfile ONBUILD instructions and can use an OnBuild strategy. source
Incremental builds
With a compatible builder image, a previous output image, a save-artifacts script, and --incremental=true, S2I can reuse artifacts from a prior build. source
Incremental builds
When a compatible prior image and save-artifacts script exist, S2I can reuse streamed build artifacts for incremental builds. source
Independent comparison criticism
Northflank describes OpenShift, where S2I is a developer workflow, as potentially expensive, complex and tied to the Red Hat ecosystem. source

Checked against the maker's pages on 15 Oct 2026.