You can rollback to previous version bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2 and wait for a fix

2 hours ago, deadnote said:

You can rollback to previous version bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2 and wait for a fix

Just getting command failed on this...unable to find image. Tried bitnami/redis:sha256-1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2 as well.

1 hour ago, silverrick said:

Just getting command failed on this...unable to find image. Tried bitnami/redis:sha256-1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2 as well.

To rollback, you will need to:

1. add a New Container

2. select the redis template you should have already

3. change the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"

4. done

For me with redis, I'm getting this error after the modification from last page

1:C 03 Jun 2026 11:44:48.982 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 03 Jun 2026 11:44:48.982 * Redis version=8.8.0, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 03 Jun 2026 11:44:48.982 * Configuration loaded
1:M 03 Jun 2026 11:44:48.983 * monotonic clock: POSIX clock_gettime
1:M 03 Jun 2026 11:44:48.986 * Running mode=standalone, port=6379.
1:M 03 Jun 2026 11:44:48.986 * Server initialized
1:M 03 Jun 2026 11:44:48.988 * Reading RDB base file on AOF loading...
1:M 03 Jun 2026 11:44:48.988 * Loading RDB produced by version 8.4.0
1:M 03 Jun 2026 11:44:48.988 * RDB age 11202523 seconds
1:M 03 Jun 2026 11:44:48.988 * RDB memory usage when created 0.97 Mb
1:M 03 Jun 2026 11:44:48.988 * RDB is base AOF
1:M 03 Jun 2026 11:44:48.989 * Done loading RDB, keys loaded: 46, keys expired: 0.
1:M 03 Jun 2026 11:44:48.991 * DB loaded from base file appendonly.aof.7.base.rdb: 0.003 seconds
1:M 03 Jun 2026 11:44:50.238 * DB loaded from incr file appendonly.aof.7.incr.aof: 1.247 seconds
1:M 03 Jun 2026 11:44:50.238 * DB loaded from append only file: 1.251 seconds
1:M 03 Jun 2026 11:44:50.238 # Can't open the AOF manifest file temp-appendonly.aof.manifest: Permission denied
1:C 03 Jun 2026 11:44:52.257 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 03 Jun 2026 11:44:52.257 * Redis version=8.8.0, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 03 Jun 2026 11:44:52.257 * Configuration loaded
1:M 03 Jun 2026 11:44:52.257 * monotonic clock: POSIX clock_gettime
1:M 03 Jun 2026 11:44:52.259 * Running mode=standalone, port=6379.
1:M 03 Jun 2026 11:44:52.259 * Server initialized
1:M 03 Jun 2026 11:44:52.261 * Reading RDB base file on AOF loading...
1:M 03 Jun 2026 11:44:52.261 * Loading RDB produced by version 8.4.0
1:M 03 Jun 2026 11:44:52.261 * RDB age 11202527 seconds
1:M 03 Jun 2026 11:44:52.261 * RDB memory usage when created 0.97 Mb
1:M 03 Jun 2026 11:44:52.261 * RDB is base AOF
1:M 03 Jun 2026 11:44:52.262 * Done loading RDB, keys loaded: 46, keys expired: 0.
1:M 03 Jun 2026 11:44:52.262 * DB loaded from base file appendonly.aof.7.base.rdb: 0.002 seconds
1:M 03 Jun 2026 11:44:53.442 * DB loaded from incr file appendonly.aof.7.incr.aof: 1.180 seconds
1:M 03 Jun 2026 11:44:53.442 * DB loaded from append only file: 1.182 seconds
1:M 03 Jun 2026 11:44:53.446 # Can't open the AOF manifest file temp-appendonly.aof.manifest: Permission denied

I tried using one of the older tag from docker hub but none work, I'm getting error about tag not found even when using copy/paste.

Without the modification, I'm getting this

redis 11:48:17.55 INFO  ==> 
redis 11:48:17.55 INFO  ==> Welcome to the Bitnami redis container
redis 11:48:17.56 INFO  ==> 
redis 11:48:17.57 INFO  ==> ** Starting Redis setup **
redis 11:48:17.59 INFO  ==> Initializing Redis
redis 11:48:17.60 INFO  ==> Setting Redis config file
chmod: changing permissions of '/opt/bitnami/redis/etc/redis.conf': Operation not permitted

Edited June 3Jun 3 by Nodiaque

4 hours ago, Probz said:

To rollback, you will need to:

1. add a New Container

2. select the redis template you should have already

3. change the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"

4. done

4 hours ago, Probz said:

To rollback, you will need to:

1. add a New Container

2. select the redis template you should have already

3. change the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"

4. done

Thanks for the suggestion. But still getting the error

[redis] 2026-06-03T13:46:54.343206320Z 1:M 03 Jun 2026 13:46:54.343 # Can't open the AOF manifest file temp-appendonly.aof.manifest: Permission denied

Honestly, since Bitnami is moving away from container and all their container will be discontinued in September it's better to just move on. I've saw another container that is using the official redis but it's lacking many configuration. I'm currently making a template from it that I successfully ran.

I deleted it and installed this one instead which works for my use with Paperless NGX because I can leave the P-NGX option to use a passwordless connection to Redis.

passwordless means protected mode off also. I'm unsure how long this will be supported. On the one I just put online, you create the config file and you have 100% control over it. There's also no persistance on that redis container

edit: there seems to be a bug with my template and I don't get why. My template put a /conf/ path but when you add it from the CA, the path is truncated. Currently investigating

Edited June 4Jun 4 by Nodiaque

On 6/3/2026 at 11:51 AM, Probz said:

To rollback, you will need to:

1. add a New Container

2. select the redis template you should have already

3. change the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"

4. done

Thanks this worked for me, my Redis is working again.

I am using this with Paperless-NGX and this template was specified by SpaceInvader1 since it has the password=no field

You could also simply take a proper redis container and use redis.Conf, and configure in that config file no password.

Problem with custom one is when the owner stop updating or remove all its container like bitnami will in September, you will be left with container without update and no recovery if you need to rebuild.

On 6/3/2026 at 11:51 AM, Probz said:

To rollback, you will need to:

1. add a New Container

2. select the redis template you should have already

3. change the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"

4. done

worked for me, too!

not sure how to migrate to another container though.

maybe someone could explain that in detail? i would not like to crash my paperless setup

honestly, you could just spin a redis native one. Once Bitnami goes down, so will all your redis container.

There's 2 I could find, the one from jj9987 which is a plain redis, no path mapping and config file. Just launch and forget (which mean no option and also not running with unraid docker user) and the one I created (there's a bug in the template, read description to fix, still waiting on return on why it's doing that) that comply with unraid user and permission.

With the one I created, you have a persistence path (which is required to backup your data) in which you can plug your current bitnami data.

The second path is the one that is bug, it should end with /config/. This is where you will put the redis.conf. The template show you where to get the redis.conf template.

After, you need to check if in the current container appdata, you have a folder "appendonlydir". If so, you need to enable appendonly in the config.

I suggest you read the config file. The default config file container run without a password in protected mode, which mean nothing can connect to it. You need to edit the file for "requiredpassword" to add a password and/or change the binding so it listen to everything. The template explain very well everything required.

I myself did it for immich, nextcloud and authelia. Moved over my 3 instances from bitnami to my container using the same config file (but different password).

Edited June 5Jun 5 by Nodiaque

Just a note about a recent issue I encountered between paperless and redis. I discovered after an update to both docker images that paperless was unable to connect with redis, apparently due to a password issue.

After some checking of redis I discovered that my original password, which had the format "worda--wordb--wordc--worde" was now listed in the redis.conf file as:
requirepass wordawordbwordcworde

I can see within the redis docker config that the "password" variable still contains the value containing double-dashes, but this latest redis update apparently strips them out.

So the fix to my paperless connectivity issue was to update its credentials to the version without dashes.

Not sure if this is an expected change in redis behaviour or a bug or a bug-fix but I hope it helps someone out.

Redis itself (at least the official docker) doesn't use environment variable. It use the config file. I strongly suggest switching to config file instead for ongoing support

I haven't seen anyone else mention the potential of moving to Valkey, which is just a continued open source fork of Redis now that its licensing is different. What's stopping us? I'm pretty sure it's a drop-in replacement and all our current containers that need redis should just be able to use it.

Edited June 10Jun 10 by Avsynthe