docs: update troubleshooting guide (#2922)

* docs: update troubleshooting guide

Add info about sumologic.setupEnable parameter in CreateContainerConfigError  troubleshooting part

* Update installation.md

docs/installation.md

@@ -368,9 +368,9 @@ rerun the `helm install` command.
 
 ### OpenTelemetry Collector Pods Stuck in CreateContainerConfigError
 
-If the OpenTelemetry Collector Pods are in `CreateContainerConfigError` it can mean the setup job has not completed yet. Wait for the setup
-pod to complete and the issue should resolve itself. The setup job creates a secret and the error simply means the secret is not there yet.
-This usually resolves itself automatically.
+If the OpenTelemetry Collector Pods are in `CreateContainerConfigError` it can mean the setup job has not been completed yet. Make sure that
+the `sumologic.setupEnable` parameter is set to `true`. Then wait for the setup pod to complete and the issue should resolve itself. The
+setup job creates a secret and the error simply means the secret is not there yet. This usually resolves itself automatically.
 
 If the issue does not solve resolve automatically, you will need to look at the logs for the setup pod. Kubernetes schedules the job in a
 pod, so you can look at logs from the pod to see why the job is failing. First find the pod name in the namespace where you installed the