Pod status as `CreateContainerConfigError` in Minikube cluster

I am trying to run Sonarqube service using the following helm chart.

So the set-up is like it starts a MySQL and Sonarqube service in the minikube cluster and Sonarqube service talks to the MySQL service to dump the data.

When I do helm install followed by kubectl get pods I see the MySQL pod status as running, but the Sonarqube pos status shows as CreateContainerConfigError. I reckon it has to do with the mounting volume thingy: link. Although I am not quite sure how to fix it (pretty nnew to Kubernetes environment and till learning 🙂 )

Related Posts:

  1. How to debug “ImagePullBackOff”?
  2. Restart container within pod
  3. My kubernetes pods keep crashing with “CrashLoopBackOff” but I can’t find any log
  4. pod has unbound PersistentVolumeClaims
  5. Unable to connect to the server: net/http: TLS handshake timeout
  6. kubectl apply vs kubectl create?
  7. Kubernetes stuck on ContainerCreating
  8. Istio Ingress resulting in “no healthy upstream”
  9. did you specify the right host or port? error on Kubernetes
  10. SonarQube Runner vs Scanner
  11. Failed to find a valid digest in the ‘integrity’ attribute for resource on a deployed emberjs application
  12. Hide Utility Class Constructor : Utility classes should not have a public or default constructor
  13. Could not find a ready tiller pod (Error)
  14. kubectl get pods shows ErrImagePull
  15. Is it possible to rerun kubernetes job?

Leave a Comment

tech