openshift-docs/modules/strategies-for-s2i-troubleshooting.adoc

// Module included in the following assemblies:
//
// * support/troubleshooting/troubleshooting-s2i.adoc

:_mod-docs-content-type: PROCEDURE
[id="strategies-for-s2i-troubleshooting_{context}"]
= Strategies for Source-to-Image troubleshooting

Use Source-to-Image (S2I) to build reproducible, Docker-formatted container images. You can create ready-to-run images by injecting application source code into a container image and assembling a new image. The new image incorporates the base image (the builder) and built source.

.Procedure

. To determine where in the S2I process a failure occurs, you can observe the state of the pods relating to each of the following S2I stages:
+
.. *During the build configuration stage*, a build pod is used to create an application container image from a base image and application source code.
+
.. *During the deployment configuration stage*, a deployment pod is used to deploy application pods from the application container image that was built in the build configuration stage. The deployment pod also deploys other resources such as services and routes. The deployment configuration begins after the build configuration succeeds.
+
.. *After the deployment pod has started the application pods*, application failures can occur within the running application pods. For instance, an application might not behave as expected even though the application pods are in a `Running` state. In this scenario, you can access running application pods to investigate application failures within a pod.

. When troubleshooting S2I issues, follow this strategy:
+
.. Monitor build, deployment, and application pod status.
+
.. Determine the stage of the S2I process where the problem occurred.
+
.. Review logs corresponding to the failed stage.