Solution to back-off restarting failed container

1. problem

pod Always restart after startup , Consolidated report Back-off restarting failed container.

principle ：

Back-off restarting failed container Of Warning event , Generally, the container is started through the specified image , There is no resident process inside the container , This causes the container to exit after it is successfully started , Thus, a continuous restart is carried out .

2. Solution

resolvent ： Find the corresponding deployment command: ["/bin/bash", "-ce", "tail -f /dev/null"]

 

apiVersion: apps/v1
kind: Deployment
metadata:
  name: test-file
  namespace: model
  labels:
    appkey: test-file
spec:
  replicas: 1
  selector:
    matchLabels:
      appkey: test-file
  template:
    metadata:
      labels:
        appkey: test-file
    spec:
      containers:
        - name: test-file
          image: xxx:v1
          command: ["/bin/bash", "-ce", "tail -f /dev/null"]
          imagePullPolicy: IfNotPresent
          volumeMounts:
          - name: test-file-data
            mountPath: /mnt
      volumes:
        - name: test-file-data
          hostPath: 
            path: /mnt