Minikube 集群中 Pod 状态为“CreateContainerConfigError"

本文介绍了Minikube 集群中 Pod 状态为“CreateContainerConfigError"的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我正在尝试使用以下 Sonarqube 服务>舵图.

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

所以设置就像它在 minikube 集群中启动 MySQL 和 Sonarqube 服务，Sonarqube 服务与 MySQL 服务对话以转储数据.

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.

当我执行 helm install 后跟 kubectl get pods 时，我看到 MySQL pod 状态为 running，但 Sonarqube pos 状态显示为 CreateContainerConfigError.我认为这与安装量有关:链接.虽然我不太确定如何修复它(对 Kubernetes 环境非常陌生，直到学习:))

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 :) )

推荐答案

这可以通过多种方式解决，我建议最好去 kubectl describe pod podname name，你现在可能会看到原因为什么您一直在尝试的服务失败了.就我而言，我发现在进行部署时配置映射中缺少我的一些键值.

This can be solved by various ways, I suggest better go for kubectl describe pod podname name, you now might see the cause of why the service that you've been trying is failing. In my case, I've found that some of my key-values were missing from the configmap while doing the deployment.