OpenShift Commons Briefing #43: Source-to-Image Deep Dive

Slight change of plans this week, we’ll be rescheduling our planned DevSecOps speaker and instead, Ben Parees - lead developer for the Source-to-Image tool chain will give us a deep dive overview into S2I and demonstrate the workflows for creating enterprise-ready reusable images.
For the latest information on OpenShift 3.2 and available briefings, please visit commons.openshi... or subscribe to the OpenShift Blog (blog.openshift...).
The OpenShift Commons exists to provide a platform for customers, partners, developers and other open source technology initiatives to collaborate, share and accelerate the pace of innovation and adoption of OpenShift globally.
The OpenShift Commons represents a new open collaborative community model designed to facilitate communication and sharing of best practices, feedback and development across the many open source initiatives that integrate with OpenShift. The best way to get involved is to join the conversation today at commons.openshi...

[@mithzeesh4806]

What is the advantage of using s2i over regular docker build?

[@VincentTubed]

and after watching an hour video, it is still not a tool that is clear in documentation and use, which the comments reflect. Why would anyone use this instead of a Dockerfile ?

[@DaleBewley]

Keep the git support in s2i. +1

[@viksin9506]

Hi, thanks for the overview. Can it be used with Azure Kubernetes Services?

[@vladimirromanovskiy9862]

What is a structure of the source in git repo?

[@AlexJanjaj]

Awesome!!!

[@TheGimboo]

Perfect tool

[@mohnishsaini5350]

HI, Thanks for the video. It clarify my concepts. I need to use python 3.5 image and connect my application MS SQL Server database hosted in some other windows server. Please assist whether we need to go for s2i or using dockerfile. Thanks

[@guiriduro]

I don't think it makes a difference, s2i / dockerfiles are just two approaches to building container images. Normally you connect to your DB at runtime.