# \`deployments-storage-daemon\` \`ImagePullBackOff\`

**URL:** <https://hub.mender.io/t/deployments-storage-daemon-imagepullbackoff/5756>\
**Category:** General Discussions\
**Tags:** kubernetes\
**Created:** [April 12, 2023, 1:31am UTC](https://hub.mender.io/t/deployments-storage-daemon-imagepullbackoff/5756 "2023-04-12T01:31:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![moto-timo](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/moto-timo/32/1736_2.png) [@moto-timo](https://hub.mender.io/u/moto-timo)\
**Post date:** [April 12, 2023, 1:31am UTC](https://hub.mender.io/t/deployments-storage-daemon-imagepullbackoff/5756/1 "2023-04-12T01:31:46Z")

</div>

After running for a while, a Mender 3.5 k8s cluster will try to create a `deployments-storage-daemon-...` pod. This tries to pull the image from `registry.mender.io/mendersoftware/deviceauth-enterprise:mender-3.5.0`, even when `enterprise: false` is set.

It seems like the following needs to be wrapped with a conditional:

> <https://github.com/mendersoftware/mender-helm/blob/1125ca164bc3b22358dcae3b2acacb0abffad51f/mender/templates/deployments-storage-daemon-cronjob.yaml#L39>

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [April 12, 2023, 12:11pm UTC](https://hub.mender.io/t/deployments-storage-daemon-imagepullbackoff/5756/2 "2023-04-12T12:11:24Z")

</div>

Hi @moto-timo,

Thanks for the report! Fixed in [this PR](https://github.com/mendersoftware/mender-helm/pull/132).

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![robgio](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/robgio/32/1760_2.png) [@robgio](https://hub.mender.io/u/robgio)\
**Post date:** [April 13, 2023, 7:46am UTC](https://hub.mender.io/t/deployments-storage-daemon-imagepullbackoff/5756/3 "2023-04-13T07:46:26Z")

</div>

Hi @moto-timo,

this is fixed in the helm chart `3.5.1` version.

Thank you  
Roberto