Crash report

1:C 15 Jun 2023 09:46:03.711 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 15 Jun 2023 09:46:03.711 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 15 Jun 2023 09:46:03.711 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 15 Jun 2023 09:46:03.712 * monotonic clock: POSIX clock_gettime
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 7.0.11 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 1
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |           https://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

1:M 15 Jun 2023 09:46:03.712 # Server initialized
1:M 15 Jun 2023 09:46:03.712 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can 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.
1:M 15 Jun 2023 09:46:03.712 # Fatal: Can't initialize Background Jobs.

Additional information

The new redis Image version 7.0.11 will crash on startup when started in AWS instance. Version 7.0.10 works fine.

  1. AWS instance tested on m4a.large and r4a.xlarge
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Docker version 20.10.7, build f0df350 docker-compose version 1.24.0, build 0aa59064

Comment From: boserup

May be related to this: https://github.com/docker-library/redis/issues/365

Comment From: Its-treason

@boserup Yes that the crash only happens with the bookworm image. Just tested with the 7.0.11-bookworm and 7.0.11-bullseye Tags. Bullseye still works and bookworm is broken.

Starting the image 7.0.11-bookworm on my local machine works, but it doesn't on an AWS instance. Both images, local and on AWS, got the same image ID: 8e69fcb59ff4

As this is not an issue with Redis itself but with the docker image, I'm closing this issue.