- Home
- Sampler Software
- Source-to-Image
Source-to-Image
What it is
Source-to-Image (S2I) is a toolkit and workflow for creating reproducible container images from source code. It places source into a builder image, lets the container prepare it for execution, and produces an image ready to run. The documented workflow can build and run from a Git repository without a Dockerfile. Builder images may provide assemble and run scripts, with optional scripts to save artifacts and describe usage. With a compatible builder, a previous output image, a save-artifacts script, and incremental mode enabled, S2I can reuse artifacts from an earlier build. A .s2iignore file can filter source files and directories, while a .s2i/environment file supplies build variables that also appear in the output image. S2I recognizes images with Dockerfile ONBUILD instructions and can use an OnBuild strategy. Documented examples use Docker and include OpenShift, UBI, Ruby, and WildFly images. The repository lists Linux, macOS, and Windows support and an Apache-2.0 license. Listed dependencies are Docker 1.6 or later and Go 1.7.1 or later; Git is optional. The toolkit is free, with no paid plans stated.
For and against
For
- Can build from a Git repository without a Dockerfile
- Supports incremental artifact reuse with compatible builders
- Filters source using a .s2iignore file
- Free toolkit with Apache-2.0 licensing
Against
- Requires Docker 1.6 or later
- Requires Go 1.7.1 or later
- Git is optional, but still a listed dependency option
The verdict
Source-to-Image provides a scripted path from source code to runnable container images, including options for filtering files and reusing build artifacts. Check its Docker and Go requirements before adopting it.
Who it suits
S2I suits developers building repeatable container images from application source, especially those using builder images and scripted build steps. It is listed for Linux, macOS, and Windows.
Plans and prices
Source-to-Image
Open-source toolkit; no paid plans stated
Read 7 Oct 2026 · github.com
On the record
- 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.github.com · read 15 Oct 2026
- Build customization
- Builder images can supply assemble and run scripts, with optional save-artifacts and usage scripts.github.com · read 7 Oct 2026
- Builder customization
- OpenShift documentation says teams can customize S2I builder images and wrap embedded scripts to add application-specific behavior.docs.redhat.com · read 15 Oct 2026
- Builder scripts
- Builder images use assemble and run scripts, with optional save-artifacts and usage scripts.github.com · read 15 Oct 2026
- Build inputs
- s2i build accepts a source location, builder image and optional output tag, with flags for environment, users, scripts and destinations.github.com · read 15 Oct 2026
- CLI commands
- The CLI documents create, build, rebuild, generate, usage, version and help commands.github.com · read 15 Oct 2026
- Company founding
- Red Hat says it was founded in 1993.redhat.com · read 15 Oct 2026
- Company headquarters
- Red Hat lists its headquarters address as 100 E. Davie Street, Raleigh, North Carolina 27601.redhat.com · read 15 Oct 2026
- Company legal name
- Crunchbase identifies the maker as Red Hat Inc., an IBM subsidiary.crunchbase.com · read 15 Oct 2026
- 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.redhat.com · read 15 Oct 2026
- Company size
- LinkedIn lists Red Hat as having more than 10,001 employees and headquarters in Raleigh, North Carolina.linkedin.com · read 15 Oct 2026
- Company workforce fact
- Red Hat's company brief reports more than 19,000 employees across 100 locations in over 40 countries.redhat.com · read 15 Oct 2026
- Dependencies
- The README lists Docker 1.6 or later and Go 1.7.1 or later as dependencies, with Git optional.github.com · read 7 Oct 2026
- 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.github.com · read 7 Oct 2026
- Dockerfile alternative
- The README demonstrates building and running an image from a Git repository without a Dockerfile.github.com · read 7 Oct 2026
- Dockerfile-free builds
- The project can build an application image directly from a Git repository without requiring a Dockerfile.github.com · read 15 Oct 2026
- Docker integration
- The documented default Docker socket is unix:///var/run/docker.sock, and S2I uses Docker client functionality for builds.github.com · read 15 Oct 2026
- Environment variables
- Values in .s2i/environment are passed into the build and remain available in the resulting application image.github.com · read 15 Oct 2026
