Pod status displays CrashLoopBackOff

[utkarshmani1997]

I made a change in prometheus-config.yaml file i.e, instead of taking image quay.io/prometheus/prometheus:v1.1.3, i am taking quay.io/prometheus/prometheus:latest also created new namespace named server so changed it accordingly.
what could be reason?

Namespace:	server
Node:		minikube/192.168.99.100
Start Time:	Mon, 04 Sep 2017 15:28:31 +0530
Labels:		name=prometheus
		pod-template-hash=766029979
Annotations:	kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"server","name":"prometheus-766029979","uid":"9b83728a-9157-11e7-90a7-0800277289ef...
		prometheus.io/port=9090
		prometheus.io/scrape=true
Status:		Running
IP:		172.17.0.4
Created By:	ReplicaSet/prometheus-766029979
Controlled By:	ReplicaSet/prometheus-766029979
Containers:
  prometheus:
    Container ID:	docker://283dafde3c003925bded8dbc097556183975c291fbbcdb7414d96a9656780702
    Image:		quay.io/prometheus/prometheus:latest
    Image ID:		docker-pullable://prom/prometheus@sha256:4bf7ad89d607dd8de2f0cff1df554269bff19fe0f18ee482660f7a5dc685d549
    Port:		9090/TCP
    Command:
      /bin/prometheus
    Args:
      -config.file=/etc/prometheus/prometheus.yml
      -storage.local.path=/prometheus
      -storage.local.retention=24h
    State:		Waiting
      Reason:		CrashLoopBackOff
    Last State:		Terminated
      Reason:		Error
      Exit Code:	1
      Started:		Mon, 04 Sep 2017 15:34:43 +0530
      Finished:		Mon, 04 Sep 2017 15:34:43 +0530
    Ready:		False
    Restart Count:	6
    Limits:
      cpu:	500m
      memory:	2500Mi
    Requests:
      cpu:		100m
      memory:		100Mi
    Environment:	<none>
    Mounts:
      /etc/prometheus from config-volume (rw)
      /prometheus from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-91zg4 (ro)
Conditions:
  Type		Status
  Initialized 	True 
  Ready 	False 
  PodScheduled 	True 
Volumes:
  data:
    Type:	EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:	
  config-volume:
    Type:	ConfigMap (a volume populated by a ConfigMap)
    Name:	prometheus-config
    Optional:	false
  default-token-91zg4:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	default-token-91zg4
    Optional:	false
QoS Class:	Burstable
Node-Selectors:	<none>
Tolerations:	<none>
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath			Type		Reason			Message
  ---------	--------	-----	----			-------------			--------	------			-------
  6m		6m		1	default-scheduler					Normal		Scheduled		Successfully assigned prometheus-766029979-kf2fz to minikube
  6m		6m		1	kubelet, minikube					Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "data" 
  6m		6m		1	kubelet, minikube					Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "config-volume" 
  6m		6m		1	kubelet, minikube					Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "default-token-91zg4" 
  6m		6m		1	kubelet, minikube	spec.containers{prometheus}	Normal		Pulling			pulling image "quay.io/prometheus/prometheus:latest"
  6m		6m		1	kubelet, minikube	spec.containers{prometheus}	Normal		Pulled			Successfully pulled image "quay.io/prometheus/prometheus:latest"
  6m		33s		7	kubelet, minikube	spec.containers{prometheus}	Normal		Created			Created container
  6m		33s		7	kubelet, minikube	spec.containers{prometheus}	Normal		Started			Started container
  6m		33s		6	kubelet, minikube	spec.containers{prometheus}	Normal		Pulled			Container image "quay.io/prometheus/prometheus:latest" already present on machine
  6m		6s		31	kubelet, minikube	spec.containers{prometheus}	Warning		BackOff			Back-off restarting failed container
  6m		6s		31	kubelet, minikube					Warning		FailedSync		Error syncing pod```

[bakins]

I need to update this repo. Hoping to have time over the holidays.