crashloopbackoff-back-off重新启动失败的容器

Question

null

apiVersion: apps/v1
kind: Deployment
metadata:
  name: sv-premier
spec:
  selector:
    matchLabels:
      app: sv-premier
  template:
    metadata:
      labels:
        app: sv-premier
    spec:
      volumes:
      - name: google-cloud-key
        secret:
          secretName: gcp-key
      containers:
      - name: sv-premier
        image: gcr.io/proto/premiercore1:latest
        imagePullPolicy: Always
        command: ["echo", "Done deploying sv-premier"]
        volumeMounts:
        - name: google-cloud-key
          mountPath: /var/secrets/google
        env:
        - name: GOOGLE_APPLICATION_CREDENTIALS
          value: /var/secrets/google/key.json
        ports:
        - containerPort: 8080
      imagePullSecrets:
      - name: imagepullsecretkey

日志-

kubectl描述pods podname

==========================

标签:APP=SV-Premier

POD-TEMPLATE-HASH=6B77DDD747

注释：

Container ID:  docker://141126d732409427fe39b405865f88856ac4e1d8586112797fc5bf4fdfbe317c

Image:         gcr.io/proto/premiercore1:latest

Image ID:      docker-pullable://gcr.io/proto/premiercore1@sha256:b3800ccca3f30725d5c9235dd349548f0fcfe309f51883d8af16397aef2c3953

Port:          8080/TCP

Host Port:     0/TCP

Command:

  echo

  Done deploying sv-premier

State:          Waiting

  Reason:       CrashLoopBackOff

Last State:     Terminated

  Reason:       Completed

  Exit Code:    0

  Started:      Tue, 04 Feb 2020 15:00:51 +0530

  Finished:     Tue, 04 Feb 2020 15:00:51 +0530

Ready:          False

Restart Count:  13

Environment:

  GOOGLE_APPLICATION_CREDENTIALS:  /var/secrets/google/key.json

Mounts:

  /var/run/secrets/kubernetes.io/serviceaccount from default-token-s4jgd (ro)

  /var/secrets/google from google-cloud-key (rw)

条件：

类型状态

初始化为真

Type:        Secret (a volume populated by a Secret)

SecretName:  gcp-key

Optional:    false

默认值-token-s4jgd:

Type:        Secret (a volume populated by a Secret)

SecretName:  default-token-s4jgd

Optional:    false

QoS类：BestEffort

节点选择器：

             node.kubernetes.io/unreachable:NoExecute for 300s

正常启动45m(x4超过46m)库贝莱特，码头-桌面启动容器sv-premier

正常拉动45米(x5超过46米）kubelet，docker-desktop拉动图像“gcr.io/proto/premiercore1:最新”

警告退避92s(x207超过46m)kubelet，Docker-桌面退避重新启动容器失败

我很困惑为什么我的容器要退出。无法启动。

请指导。

Answer 1

用一个长时间运行的任务示例更新您的deployment.yaml。

command: ["/bin/sh"]
args: ["-c", "while true; do echo Done Deploying sv-premier; sleep 3600;done"]

这将使您的容器在部署后进入睡眠状态，并且每小时都会记录一次消息。

请在此阅读有关pod生命周期容器状态的更多信息