June 3Jun 3 2 hours ago, deadnote said:You can rollback to previous version bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2 and wait for a fixJust getting command failed on this...unable to find image. Tried bitnami/redis:sha256-1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2 as well.
June 3Jun 3 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:add a New Containerselect the redis template you should have alreadychange the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"done
June 3Jun 3 For me with redis, I'm getting this error after the modification from last page1: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 deniedI 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 thisredis 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
June 3Jun 3 4 hours ago, Probz said:To rollback, you will need to:add a New Containerselect the redis template you should have alreadychange the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"done4 hours ago, Probz said:To rollback, you will need to:add a New Containerselect the redis template you should have alreadychange the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"doneThanks 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
June 3Jun 3 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.
June 4Jun 4 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.
June 4Jun 4 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 containeredit: 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
June 4Jun 4 On 6/3/2026 at 11:51 AM, Probz said:To rollback, you will need to:add a New Containerselect the redis template you should have alreadychange the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"doneThanks 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
June 4Jun 4 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.
June 5Jun 5 On 6/3/2026 at 11:51 AM, Probz said:To rollback, you will need to:add a New Containerselect the redis template you should have alreadychange the repository to: "bitnami/redis@sha256:1347d526ecec0c6537e99eac09e7c3405c21664f6044ff60e78b0898da37abd2"doneworked 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
June 5Jun 5 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
June 6Jun 6 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 wordawordbwordcwordeI 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.
June 6Jun 6 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
June 8Jun 8 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
September 10Sep 10 HI there.I run a nightly backup of my Nextcloud contents and DB using a schedule script fired via the User Scripts plugin.I received an error running my nightly DB-Backup last night.So I just ran my scheduled backup script manually and the same error appeared.Am I right in thinking a new version/Docker image was posted yesterday?My log for the Docker now shows this:**************************************************************************** * * * THIS IMAGE IS NO LONGER UPDATED AND HAS MOVED TO A NEW LOCATION * * This image is no longer maintained as of and will not receive updates. * * * * A successor image is available at: * * * * Repository | Documentation: * * - https://nfrastack.com/db-backup * * * * Image Registries: * * - https://hub.docker.com/r/nfrastack/db-backup * * - https://github.com/nfrastack/db-backup/pkgs/container/db-backup * * * * Please visit https://nfrastack.com for more information. * * * **************************************************************************** Are the two related?Do you plan to move the DB-Backup Docker to this new image?When I try to trigger a manual backup using the docker exec command, I receive the following error:root@Willow:~# docker exec db-backup backup-now OCI runtime exec failed: exec failed: unable to start container process: exec: "backup-now": executable file not found in $PATHMany thanks for your help - as well as this image.FWIW, below is the nightly script that triggers the DB-Backup:#!/bin/bash echo "Entering NextCloud maintenance mode" docker exec nextcloud occ maintenance:mode --on -q # --- DB backup (inside maintenance window so files + DB are consistent) --- echo "Backing up MariaDB via db-backup container" docker exec db-backup backup-now if [[ $? -eq 0 ]]; then echo "db-backup Process was Successful" else echo "db-backup Process was UNSUCCESSFUL" /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during DB-Backup. See log. Continuing with file backup." -i "normal" fi # --- Nextcloud files Backup --- echo "Syncing + deleting NextCloud files using rsync" rsync -Aavx --delete /mnt/cache/nextcloud/ /mnt/pool2tb/Backup/nextcloud/ #Success/failure Notification if [[ $? -eq 0 ]]; then echo "Nextcloud Files Backup Process was Successful" else echo "Nextcloud Files Backup Process was UNSUCCESSFUL" echo "Turning off maintenance mode due to error" docker exec nextcloud occ maintenance:mode --off -q /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during NextCloud Backup. See log. Maintenance mode has been turned off." -i "normal" fi echo "Exiting NextCloud maintenance mode" docker exec nextcloud occ maintenance:mode --off -q echo "Syncing + deleting changed files in photos using rsync" rsync -av --delete --exclude '.Recycle.Bin' /mnt/user/photos/ /mnt/pool2tb/Backup/photos/ #Success/failure Notification if [[ $? -eq 0 ]]; then echo "photos Backup Process was Successful" else echo "photos Backup Process was UNSUCCESSFUL" /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during Photos Backup. See log for details." -i "normal" fi echo "Syncing + deleting changed files in rpi_photos using rsync" rsync -av --delete --exclude '.Recycle.Bin' /mnt/user/rpi_photos/ /mnt/pool2tb/Backup/rpi_photos/ #Success/failure Notification if [[ $? -eq 0 ]]; then echo "rpi_photos Backup Process was Successful" else echo "rpi_photos Backup Process was UNSUCCESSFUL" /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during RPi_Photos Backup. See log for details." -i "normal" fi Again, thanks for your time, help, and maintaining this Docker image.
September 10Sep 10 56 minutes ago, jademonkee said:HI there.I run a nightly backup of my Nextcloud contents and DB using a schedule script fired via the User Scripts plugin.I received an error running my nightly DB-Backup last night.So I just ran my scheduled backup script manually and the same error appeared.Am I right in thinking a new version/Docker image was posted yesterday?My log for the Docker now shows this:**************************************************************************** * * * THIS IMAGE IS NO LONGER UPDATED AND HAS MOVED TO A NEW LOCATION * * This image is no longer maintained as of and will not receive updates. * * * * A successor image is available at: * * * * Repository | Documentation: * * - https://nfrastack.com/db-backup * * * * Image Registries: * * - https://hub.docker.com/r/nfrastack/db-backup * * - https://github.com/nfrastack/db-backup/pkgs/container/db-backup * * * * Please visit https://nfrastack.com for more information. * * * **************************************************************************** Are the two related?Do you plan to move the DB-Backup Docker to this new image?When I try to trigger a manual backup using the docker exec command, I receive the following error:root@Willow:~# docker exec db-backup backup-now OCI runtime exec failed: exec failed: unable to start container process: exec: "backup-now": executable file not found in $PATHMany thanks for your help - as well as this image.FWIW, below is the nightly script that triggers the DB-Backup:#!/bin/bashecho "Entering NextCloud maintenance mode" docker exec nextcloud occ maintenance:mode --on -q # --- DB backup (inside maintenance window so files + DB are consistent) ---echo "Backing up MariaDB via db-backup container" docker exec db-backup backup-now if [[ $? -eq 0 ]]; thenecho "db-backup Process was Successful"elseecho "db-backup Process was UNSUCCESSFUL" /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during DB-Backup. See log. Continuing with file backup." -i "normal"fi # --- Nextcloud files Backup ---echo "Syncing + deleting NextCloud files using rsync" rsync -Aavx --delete /mnt/cache/nextcloud/ /mnt/pool2tb/Backup/nextcloud/ #Success/failure Notificationif [[ $? -eq 0 ]]; thenecho "Nextcloud Files Backup Process was Successful"elseecho "Nextcloud Files Backup Process was UNSUCCESSFUL"echo "Turning off maintenance mode due to error" docker exec nextcloud occ maintenance:mode --off -q /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during NextCloud Backup. See log. Maintenance mode has been turned off." -i "normal"fi echo "Exiting NextCloud maintenance mode" docker exec nextcloud occ maintenance:mode --off -q echo "Syncing + deleting changed files in photos using rsync" rsync -av --delete --exclude '.Recycle.Bin' /mnt/user/photos/ /mnt/pool2tb/Backup/photos/ #Success/failure Notificationif [[ $? -eq 0 ]]; thenecho "photos Backup Process was Successful"elseecho "photos Backup Process was UNSUCCESSFUL" /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during Photos Backup. See log for details." -i "normal"fi echo "Syncing + deleting changed files in rpi_photos using rsync" rsync -av --delete --exclude '.Recycle.Bin' /mnt/user/rpi_photos/ /mnt/pool2tb/Backup/rpi_photos/ #Success/failure Notificationif [[ $? -eq 0 ]]; thenecho "rpi_photos Backup Process was Successful"elseecho "rpi_photos Backup Process was UNSUCCESSFUL" /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Nightly Backup" -d "ERROR during RPi_Photos Backup. See log for details." -i "normal"fiAgain, thanks for your time, help, and maintaining this Docker image.Ok, I changed the Docker tag from :latest to :4.1.100 (the previous version) and the backups now work again.So my only question now is: will you move the Docker image in the Unraid App Store to the new 5.0 version described at https://github.com/nfrastack/db-backup?Many thanks. Edited September 10Sep 10 by jademonkee typo
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.