# Debugging a failing image without a deployment

**URL:** <https://community.fly.io/t/debugging-a-failing-image-without-a-deployment/1545>\
**Category:** General\
**Created:** [May 25, 2021, 6:08pm UTC](https://community.fly.io/t/debugging-a-failing-image-without-a-deployment/1545 "2021-05-25T18:08:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [May 25, 2021, 6:25pm UTC](https://community.fly.io/t/debugging-a-failing-image-without-a-deployment/1545/4 "2021-05-25T18:25:32Z")

</div>

You should be able to use that URL for `REDIS_CACHE_URL`.

We _probably_ won’t make that magical, our shared Redis cache has been deprecated and people are better off running redis processes themselves for the most part. We might introduce a `fly redis` command that behaves like Postgres, though, it’s relatively straightforward.

---

_[View the full topic](https://community.fly.io/t/debugging-a-failing-image-without-a-deployment/1545)._