redis not starting (after update to 9.1.3?)

[AdMo]

Hello,

my Cloudron instance updated last night to 9.1.3 and many of my apps are not starting due to "plattform start" not finished.
Looking at the services I found the redis not starting up in the context of one container (pixelfed). In the log I found this:

• cloudron-support --troubleshoot:

Vendor: QEMU Product: Standard PC (i440FX + PIIX, 1996)
Linux: 6.8.0-101-generic
Ubuntu: noble 24.04
Execution environment: kvm
Processor: 13th Gen Intel(R) Core(TM) i9-13900H
BIOS pc-i440fx-10.1  CPU @ 2.0GHz x 8
RAM: 32859228KB
Disk: /dev/sda2       2.7T
[OK]	node version is correct
[OK]	IPv6 is enabled in kernel. No public IPv6 address
[OK]	docker is running
[OK]	docker version is correct
[OK]	MySQL is running
[OK]	netplan is good
[OK]	DNS is resolving via systemd-resolved
	Service 'unbound' just started 7 secs ago, checking health again in 10s
[OK]	unbound is running
[OK]	nginx is running
[OK]	dashboard cert is valid
[OK]	dashboard is reachable via loopback
[FAIL]	Database migrations are pending. Last migration in DB: /20260217120000-mailPasswords-create-table.js. Last migration file: /package.json.
	Please run 'cloudron-support --apply-db-migrations' to apply the migrations.
[OK]	Service 'mysql' is running and healthy
[OK]	Service 'postgresql' is running and healthy
[OK]	Service 'mongodb' is running and healthy
[OK]	Service 'mail' is running and healthy
[OK]	Service 'graphite' is running and healthy
[OK]	Service 'sftp' is running and healthy
[OK]	box v9.1.3 is running
[FAIL]	Could not load dashboard domain.
Hairpin NAT is not working. Please check if your router supports it

Running 'cloudron-support --apply-db-migrations' (several times) didn't help. From '/home/yellowtent/platformdata/logs/box.log':

...
2026-03-09T17:43:51.873Z box:services Waiting for redis-33711a7d-a850-4163-9678-6c37aba763a8
2026-03-09T17:43:51.875Z box:services Attempt 1 failed. Will retry: Network error waiting for redis-33711a7d-a850-4163-9678-6c37aba763a8: connect ECONNREFUSED 172.18.0.2:3000 
2026-03-09T17:44:07.058Z box:services startRedis: stopping and deleting previous redis container redis-693839fe-6d93-4bec-8963-ba45f18ffc2e
2026-03-09T17:44:07.058Z box:docker stopContainer: stopping container redis-693839fe-6d93-4bec-8963-ba45f18ffc2e
2026-03-09T17:44:09.550Z box:docker deleteContainer: deleting redis-693839fe-6d93-4bec-8963-ba45f18ffc2e
2026-03-09T17:44:09.700Z box:services startRedis: starting redis container redis-693839fe-6d93-4bec-8963-ba45f18ffc2e
2026-03-09T17:44:09.752Z box:shell services: /bin/bash -c docker run -d --restart=unless-stopped --name=redis-693839fe-6d93-4bec-8963-ba45f18ffc2e                 --hostname redis-693839
fe-6d93-4bec-8963-ba45f18ffc2e                 --label=location=mastodon.moik.cloud                 --net cloudron                 --net-alias redis-693839fe-6d93-4bec-8963-ba45f18ffc2e 
                --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424        
         --log-opt tag=redis-693839fe-6d93-4bec-8963-ba45f18ffc2e                 -m 4294967296                 --memory-swap -1                 -e CLOUDRON_REDIS_PASSWORD
                 -e CLOUDRON_REDIS_TOKEN=[...]                -v /home/yellowtent/platformdata/redis/693839f
e-6d93-4bec-8963-ba45f18ffc2e:/var/lib/redis                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.8.0@sha256:54
a12252edbc326fd4d10e8c00836cc68776f3463f22366279f7cd8d4dafd20f 
2026-03-09T17:44:10.579Z box:services Waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e
2026-03-09T17:44:30.583Z box:services Attempt 1 failed. Will retry: Network error waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e: The operation was aborted 
2026-03-09T17:45:05.585Z box:services Attempt 2 failed. Will retry: Network error waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e: The operation was aborted 
2026-03-09T17:45:40.585Z box:services Attempt 3 failed. Will retry: Network error waiting for redis-693839fe-6d93-4bec-8963-ba45f18ffc2e: The operation was aborted 

It seems that redis can't write to /run/redis:

Mar 09 19:24:45 2026-03-09 18:24:45,052 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
Mar 09 19:24:45 2026-03-09 18:24:45,052 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
Mar 09 19:24:45 2026-03-09 18:24:45,052 INFO Set uid to user 0 succeeded
Mar 09 19:24:45 2026-03-09 18:24:45,056 INFO RPC interface 'supervisor' initialized
Mar 09 19:24:45 2026-03-09 18:24:45,056 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Mar 09 19:24:45 2026-03-09 18:24:45,056 INFO supervisord started with pid 1
Mar 09 19:24:46 2026-03-09 18:24:46,059 INFO spawned: 'redis' with pid 13
Mar 09 19:24:46 2026-03-09 18:24:46,060 INFO spawned: 'redis-service' with pid 14
Mar 09 19:24:46 13:C 09 Mar 2026 18:24:46.066 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Mar 09 19:24:46 13:C 09 Mar 2026 18:24:46.067 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Mar 09 19:24:46 13:C 09 Mar 2026 18:24:46.067 * Redis version=8.4.0, bits=64, commit=00000000, modified=1, pid=13, just started
Mar 09 19:24:46 13:C 09 Mar 2026 18:24:46.067 * Configuration loaded
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.067 * Increased maximum number of open files to 10032 (it was originally set to 1024).
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.067 * monotonic clock: POSIX clock_gettime
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.068 # Failed to write PID file: Permission denied
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.068 * Running mode=standalone, port=6379.
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.068 * Server initialized
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.070 * Loading RDB produced by version 8.4.0
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.070 * RDB age 335 seconds
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.070 * RDB memory usage when created 0.83 Mb
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.073 * Done loading RDB, keys loaded: 112, keys expired: 0.
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.073 * DB loaded from disk: 0.005 seconds
Mar 09 19:24:46 13:M 09 Mar 2026 18:24:46.073 * Ready to accept connections tcp
Mar 09 19:24:46 Redis service endpoint listening on http://:::3000
Mar 09 19:24:47 2026-03-09 18:24:47,183 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Mar 09 19:24:47 2026-03-09 18:24:47,183 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Any ideas?
Thanks.

Maybe it is not the best idea not to start many of the other apps when just one redis service isn't starting up...

BR
Adam