Which password does the container actually use?
The bundled installer writes requirepass only when DATA_DIR/conf/redis.conf does not exist. On another run it can accept or generate a different password, retain the existing file, and print the new variable. That output does not change the mounted configuration.
This is a source-derived failure candidate, not a diagnosis of your host. Determine which config file is mounted and consult its effective password through your private credential process. Redis 7.0.5 is a historical compatibility target, not a current-version recommendation.
Verify mounts and the actual reply
Use the actual container name in these read-only examples. Enter the password at the masked prompt and look for PONG. The installer checks redis-cli exit status, not the PONG contents; an overall completion banner is weaker evidence than a successful authenticated reply.
Keep redis.conf, data and any backups until the cause is understood. Supplying --password again does not rotate an existing file. The script can force-remove the container and prints credentials, so retries and shared output need a reviewed maintenance process.
- docker inspect redis705 --format '{{json .Mounts}}'
- docker exec -it redis705 redis-cli --askpass PING