kubernetes - 如何执行到初始化容器?

标签 kubernetes kubernetes-helm

$ kubectl version

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:21:50Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

看着Sonarqube helm chart

要求.yaml
dependencies:
- name: sonarqube
  version: 0.5.0
  repository: https://kubernetes-charts.storage.googleapis.com/

尝试安装最新版本的 java 插件:

values.yaml
plugins:
   install:
     - "http://central.maven.org/maven2/org/sonarsource/java/sonar-java-plugin/5.3.0.13828/sonar-java-plugin-5.3.0.13828.jar"

但是,我在 init 容器上遇到错误:
$ kubectl logs sonarqube-sonarqube-7b5dfd84cf-sglk5 -c install-plugins

sh: /opt/sonarqube/extensions/plugins/install_plugins.sh: Permission denied
$ kubectl describe po sonarqube-sonarqube-7b5dfd84cf-sglk5

Name:           sonarqube-sonarqube-7b5dfd84cf-sglk5
Namespace:      default
Node:           docker-for-desktop/192.168.65.3
Start Time:     Thu, 19 Apr 2018 15:22:04 -0500
Labels:         app=sonarqube
                pod-template-hash=3618984079
                release=sonarqube
Annotations:    <none>
Status:         Pending
IP:             10.1.0.250
Controlled By:  ReplicaSet/sonarqube-sonarqube-7b5dfd84cf
Init Containers:
  install-plugins:
    Container ID:  docker://b090f52b95d36e03b8af86de5a6729cec8590807fe23e27689b01e5506604463
    Image:         joosthofman/wget:1.0
    Image ID:      docker-pullable://joosthofman/wget@sha256:74ef45d9683b66b158a0acaf0b0d22f3c2a6e006c3ca25edbc6cf69b6ace8294
    Port:          <none>
    Command:
      sh
      -c
      /opt/sonarqube/extensions/plugins/install_plugins.sh
    State:          Waiting
      Reason:       CrashLoopBackOff

有没有办法到exec进入 init 容器?

我的尝试:
$ kubectl exec -it sonarqube-sonarqube-7b5dfd84cf-sglk5 -c install-plugins sh

error: unable to upgrade connection: container not found ("install-plugins")

更新

根据@WarrenStrange 的建议:
$ kubectl get pods
NAME                                    READY     STATUS    RESTARTS   AGE
sonarqube-postgresql-59975458c6-mtfjj   1/1       Running   0          11m
sonarqube-sonarqube-685bd67b8c-nmj2t    1/1       Running   0          11m

$ kubectl get pods sonarqube-sonarqube-685bd67b8c-nmj2t -o yaml
...
 initContainers:
  - command:
    - sh
    - -c
    - 'mkdir -p /opt/sonarqube/extensions/plugins/ && cp /tmp/scripts/install_plugins.sh
      /opt/sonarqube/extensions/plugins/install_plugins.sh && chmod 0775 /opt/sonarqube/extensions/plugins/install_plugins.sh
      && /opt/sonarqube/extensions/plugins/install_plugins.sh '
    image: joosthofman/wget:1.0
    imagePullPolicy: IfNotPresent
    name: install-plugins
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /opt/sonarqube/extensions
      name: sonarqube
      subPath: extensions
    - mountPath: /tmp/scripts/
      name: install-plugins
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-89d9n
      readOnly: true
...

创建从 init 容器 list 中提取的新 pod list 。将命令替换为 sleep 6000并执行命令。这使您可以四处闲逛。

最佳答案

问题是容器不存在(请参阅 CrashLoopBackOff)。

我对 init 容器所做的一件事(假设您有源)是在入口点失败时设置 sleep 600。至少用于调试。这使您可以 exec 进入容器以查看失败的原因。

关于kubernetes - 如何执行到初始化容器?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/49929826/

相关文章:

kubernetes - kubectl status.phase=运行返回错误结果

azure - 如何在 Kubernetes (AKS) 中使用 Helm 注释 Ingress Controller 的 Pod?

elasticsearch - Helm chart 稳定/logstash-在同一ns中看不到elasticsearch

kubernetes - helm 模板语言中的全局变量以避免重复

故障转移后 MySQL 节点加入组复制失败导致额外事务

azure - 创建集群后将 RBAC 添加到 Azure Kubernetes (AKS)

docker - 日志是否保存在Google Kubernetes上

kubernetes - 如何在prometheus-operator中监控外部服务

kubernetes - Minikube 集群中的 Pod 状态为 `CreateContainerConfigError`

azure - Azure 上的 Kubernetes : connectex