# Upgrade to 3.0.2: NameError: undefined method \`call' for class \`Redis::Client' (with a "fix")

**URL:** <https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [March 18, 2023, 5:07pm UTC](https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602 "2023-03-18T17:07:33Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [March 21, 2023, 6:25pm UTC](https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602/8 "2023-03-21T18:25:54Z")

</div>

> [@steinhh](#):
>
> Yes, doing it the official way would almost certainly have given me fewer headaches (most likely none). The problem is that I’m not allowed to use docker images that are not pre-approved by our IT security department - and yours is not.

You might suggest to your security team that an image that is vetted and used by the developers is much, much safer than your attempting to apply security patches to things that you can’t possibly keep track of unless it’s your only job.

. . . . But, that’s likely not helpful.

---

_[View the full topic](https://meta.discourse.org/t/upgrade-to-3-0-2-nameerror-undefined-method-call-for-class-redis-client-with-a-fix/258602)._