"CrashLoopBackOff" error

General Discussions
1

Looking for some assistance the “CrashLoopBackOff” container error when creating a deployment. I’m not getting any log details since the container never starts.

Cluster information:

Kubernetes version: v1.29
Cloud being used:AWS EKS
Installation method:
Host OS:
CNI and version: amazon k8s 1.17
CRI and version: containerd: 1.7.11

Hello all, Super new to kubernetes
Looking for some assistance the “CrashLoopBackOff” container error when creating a deployment. I’m not getting any log details since the container never starts.
Using the a image: nginx:1.14.2 image everything starts up without issue. but once I use the amazonlinux image I get “CrashLoopBackOff”

apiVersion: apps/v1
kind: Deployment
metadata:
  name: test-deployment
  namespace: devops-tools
  labels:
    app: my-test
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-test
  template:
    metadata:
      labels:
        app: my-test
    spec:
      containers:
        - name: my-test-container
          image: nginx:1.14.2
          ports:
            - containerPort: 22

test-deployment-598b5b7fbb-r9tm2 1/1 Running 0 8s

changing the image to amazonlinuz

containers:
        - name: my-test-container
          image: amazonlinux:latest
          ports:
            - containerPort: 22

test-deployment-84f986b49c-lcq8p 0/1 CrashLoopBackOff 1 (3s ago) 12s

Any help would be appreciated. Could this be the node group? are there any other logs I can look into

Here are the generated events

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  2m47s                 default-scheduler  Successfully assigned devops-tools/test-deployment-84f986b49c-lcq8p to ip-192-168-7-18.ec2.internal
  Normal   Pulled     2m45s                 kubelet            Successfully pulled image "amazonlinux:latest" in 1.865s (1.865s including waiting)
  Normal   Pulled     2m38s                 kubelet            Successfully pulled image "amazonlinux:latest" in 6.469s (6.469s including waiting)
  Normal   Pulled     2m22s                 kubelet            Successfully pulled image "amazonlinux:latest" in 133ms (133ms including waiting)
  Normal   Created    117s (x4 over 2m45s)  kubelet            Created container my-test-container
  Normal   Started    117s (x4 over 2m45s)  kubelet            Started container my-test-container
  Normal   Pulled     117s                  kubelet            Successfully pulled image "amazonlinux:latest" in 115ms (115ms including waiting)
  Warning  BackOff    77s (x8 over 2m37s)   kubelet            Back-off restarting failed container my-test-container in pod test-deployment-84f986b49c-lcq8p_devops-tools(159d6b9c-d2b0-450b-aaab-12667ed28a8c)
  Normal   Pulling    64s (x5 over 2m46s)   kubelet            Pulling image "amazonlinux:latest"
2

I was able to fix this by creating my own image and adding the

ENTRYPOINT ["tail", "-f", "/dev/null"]