Redis [CRASH] Docker Image 'arm64v8/redis' cannot startup with log 'Failed to test the kernel for a bug that could lead to data corruption during background save.'

Crash report I'm now trying to download latest arm64v8 Redis image and deploy. Then I get error and cannot startup the container. I have added 'ignore-warnings ARM64-COW-BUG' in my config file, and the error log is not related with it. I also added 'save ""' to ignore persistence of the data.

Can someone help to give me any suggestion or support?

Redis version:

"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", 
"GOSU_VERSION=1.17", 
"REDIS_VERSION=7.2.5", 
"REDIS_DOWNLOAD_URL=http://download.redis.io/releases/redis-7.2.5.tar.gz", 
"REDIS_DOWNLOAD_SHA=5981179706f8391f03be91d951acafaeda91af7fac56beffb2701963103e423d"

Docker run script:

docker run -it \
  --name redis_singleton \
  -p 6379:6379 \
  -v /mnt/usb/volumes/redis_singleton/conf:/usr/local/etc/redis \
  -v /mnt/usb/volumes/redis_singleton/logs:/var/log/redis \
  -v /mnt/usb/volumes/redis_singleton/data/:/data \
  --user root \
  --workdir /usr/local \
  arm64v8/redis \
  redis-server /usr/local/etc/redis/redis.conf

redis.conf:

daemonize yes
port 6379
bind 0.0.0.0
logfile ""
dir "/data"
dbfilename "dump.rdb"
save ""
maxmemory 512mb
maxmemory-policy allkeys-lru
appendonly yes
appendfilename "appendonly.aof"
appendfsync everysec
ignore-warnings ARM64-COW-BUG

Docker logs:

/data #  docker logs -f redis_singleton
1:C 06 Jul 2024 14:21:35.794 # Failed to test the kernel for a bug that could lead to data corruption during background save. Your system could be affected, please report this error.
1:C 06 Jul 2024 14:26:12.362 # Failed to test the kernel for a bug that could lead to data corruption during background save. Your system could be affected, please report this error.

Additional information

OS distribution and version

root@XiaoQiang:/mnt/usb-56ac155b/volumes/redis_singleton/conf# uname -a
Linux XiaoQiang 5.4.164 #0 SMP PREEMPT Thu Dec 21 01:45:39 2023 aarch64 GNU/Linux

Steps to reproduce (if any)

Comment From: sundb

we shouldn't use daemonize yes in docker, docker need a foreground process.

Comment From: yangshuyi

we shouldn't use daemonize yes in docker, docker need a foreground process.

You are correct. Thank you for your kindly help.