[Bug]: Port 6379 conflicts with local port. Can I specify the Redis port in Docker

[nmww]

docker run -d
-p 11235:11235
--name crawl4ai
--shm-size=3g
unclecode/crawl4ai:latest

2025-08-22 08:44:28,697 INFO supervisord started with pid 1 2025-08-22 08:44:29,700 INFO spawned: 'redis' with pid 7 2025-08-22 08:44:29,704 INFO spawned: 'gunicorn' with pid 8 7:C 22 Aug 2025 08:44:29.725 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 7:C 22 Aug 2025 08:44:29.725 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=7, just started 7:C 22 Aug 2025 08:44:29.725 # Configuration loaded 7:M 22 Aug 2025 08:44:29.726 * monotonic clock: POSIX clock_gettime 7:M 22 Aug 2025 08:44:29.727 * Running mode=standalone, port=6379. 7:M 22 Aug 2025 08:44:29.728 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 7:M 22 Aug 2025 08:44:29.728 # Server initialized 7:M 22 Aug 2025 08:44:29.728 # 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. 7:M 22 Aug 2025 08:44:29.729 * Ready to accept connections 2025-08-22 08:44:30,731 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-08-22 08:44:30,731 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

The connection cannot be established, this usually occurs due to an incorrect host (domain) value