# Back-off restarting failed container ..imageID or ContainerID not generated

**URL:** <https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809>\
**Category:** Using Jenkins\
**Tags:** docker\
**Created:** [September 16, 2022, 5:31am UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809 "2022-09-16T05:31:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![cloudshashi](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@cloudshashi](https://community.jenkins.io/u/cloudshashi)\
**Post date:** [September 16, 2022, 5:31am UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/1 "2022-09-16T05:31:19Z")

</div>

Hi,  
I am using helm charts to install jenkins in kubernetes pod and getting an error “Back-off restarting failed container”. This was working till yeasterday, no modification done. How to make sure that ImageID/ContainerID generates to solve this pod issue ?

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [September 17, 2022, 2:43am UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/2 "2022-09-17T02:43:56Z")

</div>

Take a look at the logs for that pod. Also describe that pod. Both should give you more info.

---

<div class="post-metadata">

**Author:** ![cloudshashi](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@cloudshashi](https://community.jenkins.io/u/cloudshashi)\
**Post date:** [September 20, 2022, 11:05am UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/3 "2022-09-20T11:05:20Z")

</div>

yes, it is because of plugins . I have removed plugins from chart (template) and re-added… now it is working fine.

---

<div class="post-metadata">

**Author:** ![Deba-shis](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/deba-shis/32/8561_2.png) [@Deba-shis](https://community.jenkins.io/u/Deba-shis)\
**Post date:** [June 7, 2024, 7:11pm UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/4 "2024-06-07T19:11:30Z")

</div>

facing same issue, any one have any solution for this

Normal Pulled 77s kubelet Successfully pulled image “[docker.io/jenkins/jenkins:2.452.1-jdk17](http://docker.io/jenkins/jenkins:2.452.1-jdk17)” in 1.46s (1.46s including waiting). Image size: 282550266 bytes.  
Normal Pulling 50s (x4 over 93s) kubelet Pulling image “[docker.io/jenkins/jenkins:2.452.1-jdk17](http://docker.io/jenkins/jenkins:2.452.1-jdk17)”  
Normal Created 49s (x4 over 92s) kubelet Created container init  
Normal Started 49s (x4 over 91s) kubelet Started container init  
Normal Pulled 49s kubelet Successfully pulled image  
Warning BackOff 24s (x6 over 89s) kubelet Back-off restarting failed container init in pod jenkins-0\_jenkins(471f6d1a-46ad-421a-9158-040a28ef3056)

---

<div class="post-metadata">

**Author:** ![rjshk013](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/rjshk013/32/10649_2.png) [@rjshk013](https://community.jenkins.io/u/rjshk013)\
**Post date:** [October 4, 2024, 2:00pm UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/5 "2024-10-04T14:00:37Z")

</div>

I was also facing the issue.I checked the init container logs & it showed there are some issues with the plugins present in my helm values.yaml.I updated one problem causing plugin version as per the init container logs & the jenkins started properly

---

<div class="post-metadata">

**Author:** ![rjshk013](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/rjshk013/32/10649_2.png) [@rjshk013](https://community.jenkins.io/u/rjshk013)\
**Post date:** [October 4, 2024, 2:01pm UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/6 "2024-10-04T14:01:26Z")

</div>

Yes.This helped to fix the issue.Thanks @cloudshashi

---

<div class="post-metadata">

**Author:** ![WCYa](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/wcya/32/18376_2.png) [@WCYa](https://community.jenkins.io/u/WCYa)\
**Post date:** [November 27, 2025, 1:23pm UTC](https://community.jenkins.io/t/back-off-restarting-failed-container-imageid-or-containerid-not-generated/3809/7 "2025-11-27T13:23:33Z")

</div>

I was experiencing the same issue.

When I checked the InitContainer (init) logs, I found the process stalling at the overwrite inquiry:

```auto
copy plugins to shared volume
cp: overwrite '/var/jenkins_plugins/antisamy-markup-formatter.jpi'? ...

```

In the apply\_config.sh script within the jenkins ConfigMap, the original command was:

[repo template](https://github.com/jenkinsci/helm-charts/blob/6c2606f8ce4e5189b124c65b07a3323f843379c9/charts/jenkins/templates/config.yaml#L47)

```auto
echo "copy plugins to shared volume"
# Copy plugins to shared volume
yes n | cp -i /usr/share/jenkins/ref/plugins/* /var/jenkins_plugins/;
echo "finished initialization"

```

I thinked the problem was with the cp -i command.

I changed the command to use cp -n instead:

```auto
cp -n /usr/share/jenkins/ref/plugins/* /var/jenkins_plugins/;

```

After modifying the configuration and restarting the kubernetes cluster, the jenkins pod worked fine.