kubernetes error - Back-off restarting failed container

[metturarun]

Hi,

I have created Docker image and pushed to AWS ECR. When trying to pull the image from ECR, during pod creation in kubernetes (v 1.9.0) getting the error "Back-off restarting failed container"

Below steps, i followed.

1. Docker pull centos 7

2. Then ssh to the container and installed oracle java 8. Then commit the image. Pushed to ECR.

when try to create Replication controller. Getting the error above mentioned.

my replicationcontroller yaml file below

apiVersion: v1
kind: ReplicationController
metadata:
name: springboot-dev
spec:
replicas: 3
template:
metadata:
name: springboot-dev
namespace: default
labels:
env: springboot-dev
spec:
containers:
- name: springboot-dev
image: xxxxx5.dkr.ecr.eu-central-1.amazonaws.com/repo:ubuntu16-java8
resources:
limits:
memory: "2000Mi"
requests:
memory: "1000Mi"
volumeMounts:
- name: springboot-jar
mountPath: "/var/www/jar"
volumes:
- name: springboot-jar
persistentVolumeClaim:
claimName: springboot-dev-pvc1
nodeSelector:
noderole: appservernode

[metturarun]

kubectl describe pod springboot-dev-664fd9f9ff-kmx9n
Name: springboot-dev-664fd9f9ff-kmx9n
Namespace: default
Node: ip-172-20-63-96.eu-central-1.compute.internal/172.20.63.96
Start Time: Tue, 27 Mar 2018 12:50:33 +0400
Labels: env=springboot-dev
pod-template-hash=2209859599
Annotations: kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container springboot-dev
Status: Running
IP: 100.96.4.31
Controlled By: ReplicaSet/springboot-dev-664fd9f9ff
Containers:
springboot-dev:
Container ID: docker://6daedb967c311b0fc592d9355e7a3a651982c31d7d6c0250279da211c12d064f
Image: 859544260695.dkr.ecr.eu-central-1.amazonaws.com/bmrrepo:ubuntu16-java8
Image ID: docker-pullable://859544260695.dkr.ecr.eu-central-1.amazonaws.com/bmrrepo@sha256:537bede2dbefe6f2894ce02146d28f05d0a67772b28d3b79402c5666bea7096b
Port:
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Completed
Exit Code: 0
Started: Tue, 27 Mar 2018 12:56:36 +0400
Finished: Tue, 27 Mar 2018 12:56:36 +0400
Ready: False
Restart Count: 6
Limits:
memory: 2000Mi
Requests:
cpu: 100m
memory: 1000Mi
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-58x8c (ro)
/var/www/jar from springboot-jar (rw)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
springboot-jar:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: springboot-dev-pvc1
ReadOnly: false
default-token-58x8c:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-58x8c
Optional: false
QoS Class: Burstable
Node-Selectors: noderole=appservernode
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message

---

Normal Scheduled 7m default-scheduler Successfully assigned springboot-dev-664fd9f9ff-kmx9n to ip-172-20-63-96.eu-central-1.compute.internal
Normal SuccessfulMountVolume 7m kubelet, ip-172-20-63-96.eu-central-1.compute.internal MountVolume.SetUp succeeded for volume "default-token-58x8c"
Normal SuccessfulMountVolume 6m kubelet, ip-172-20-63-96.eu-central-1.compute.internal MountVolume.SetUp succeeded for volume "pvc-5d8aa5d9-30e6-11e8-ab26-0242c1ea278c"
Normal Pulled 5m (x5 over 6m) kubelet, ip-172-20-63-96.eu-central-1.compute.internal Container image "859544260695.dkr.ecr.eu-central-1.amazonaws.com/bmrrepo:ubuntu16-java8" already present on machine
Normal Created 5m (x5 over 6m) kubelet, ip-172-20-63-96.eu-central-1.compute.internal Created container
Normal Started 5m (x5 over 6m) kubelet, ip-172-20-63-96.eu-central-1.compute.internal Started container
Warning BackOff 2m (x22 over 6m) kubelet, ip-172-20-63-96.eu-central-1.compute.internal Back-off restarting failed container